Hi
Check your settings for these values in tcode OB40
I hope it helps you
Regards
Eduardo
Hi
Check your settings for these values in tcode OB40
I hope it helps you
Regards
Eduardo
Hi Muni,
Based on recommendations provided in SAP Help materials for "Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite" in part of employee data replication (refer to SuccessFactors Integration: Employee Data Replication - Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite …), usage of RH_SFI_SYNCHRONIZE_EMPL_DATA is a preferred option in comparison with RH_SFI_TRIGGER_EMPL_DATA_REPL. RH_SFI_SYNCHRONIZE_EMPL_DATA provides features for delta extraction and integration with SuccessFactors not only via files, but also via middleware (both are not available in RH_SFI_TRIGGER_EMPL_DATA_REPL).
You are right, usage of RH_SFI_SYNCHRONIZE_EMPL_DATA in combination with middleware based integration will involve three interfaces:
All these interfaces are provided as a part of SAP add-on for integration between HCM and SuccessFactors, and RH_SFI_TRIGGER_EMPL_DATA_REPL implements calls of these three interfaces in required sequence (SFSFSessionHandlingLoginQueryResult_Out, followed by SFSFUserUpsertRequestConfirmation_Out and SFSFSessionHandlingLogoutQueryResult_Out), and since login and logout interfaces are very lightweight, they shouldn't bring much overhead to entire integration.
You are correct: not all scenarios which are currently delivered in SAP add-on content, make use of SuccessFactors adapter currently, so drawback is necessity of usage of Axis adapter for quite a lot of them at the moment, if we would like to utilize SAP standard configuration as much possible.
In my opinion, even though usage of Axis based solution requires extra overhead related to deployment of Axis libraries and involves two extra interfaces, I would prefer that one in order to make use of SAP standard configuration scenarios delivered in add-on as much as possible - at least for current being, until they are not migrated to SuccessFactors adapter. If some time in the future they will be complemented or replaced by those using SuccessFactors adapter and delivered in SAP add-on, I would definitely prefer SuccessFactors adapter based rather than Axis adapter based. File based integration is the least preferred method by me in this particular scenario between discussed three options.
Regards,
Vadim
Hi
Please, see also note 1561427 - Billing document split
I hope it helps you
Regards
Eduardo
Thank you Vadim.
Hello Veera
I think you can raise this as an enhancement request: https://ideas.sap.com/SAPDisclosureManagement
Regards,
Marc
We have outsource our COBRA Plan to third party provider. They did provide us the coverage information for COBRA coverage for the year. My question is, is there an easy way to load that information in ACA Tables?
Hi zoltan thanks for you help . so that scenary is not covert on standard but do you commented if its posible obtain with enhacements . could you explain if you know more about that
Thanks
Hi Don,
Thank you so much for your time and help!
Frank
Thanks Dave.
I will go through your document and keep digging on SCN.
I appreciate your help.
Regards,
Destine
Hi
That new error seems to be a known issue that is fixed in Revision 100 and higher.
The workaround to resolve it is to perform an unload of the table, e.g.
"UNLOAD TABLE <schema_name>. <table_name>" and Restart the database
For instructions on Load/Unload a Column Table into/from Memory:
http://help.sap.com/saphelp_hanaplatform/helpdata/en/c1/33165bbb57101493c5fb19b5b8607f/content.htm
To prevent it from happening normally you can perform an unload of the table, see above. Unloading and re-loading will prevent that the issue occurs at all.
For a permanent solution you can upgrade to SAP HANA Revision 100 and higher
Please note that: Before adding columns to a table in productive systems, which may happen in the context of
ABAP transports, plan accordingly in order to avoid unforeseen downtimes. Ideally unload relevant tables first
before applying transports to avoid subsequent activation errors.
Cheers
Kingsley
Hi there!
Any progress?
The problem may be on the SalesPriceList BO. The query don't work even by the Repository Explorer interface (HTTP 500 (InternalServerError) in SalesPriceList BO. )
I'm trying to query by code and it doesn't build =/. The SDK says that the parameters does not exist.
Thanks in advance.
Look on the note http://service.sap.com/sap/support/notes/2107965
Dear Arun,
I guess u have not understood the problem, i mentioned that i am joining output data set of a query transform and SAP table, while joining the two, i am not able to see the SAP table in Smart Editor for writing the joining conditions, please refer to the screenshot i have attached in the original discussion.
Hi Ronny
as I know it is not possible to add lines in Delivery Notes. You can only change some values if the line is still open and there's no target document linked.
Generally what you can do inside SAP Business One can be done using DI api and vice-versa.
B1if uses DI api to manipulate database.
Regards,
Pierre
Hi Charusmita,
As per my knowledge goes, some European countries, have a long bank account number, (See Note 1585003) containing country code (first 2 characters), bank number and bank account number.
SAP uses a special functionality for these IBAN's: it stores the old account number in master data (also called BBAN: Basic Bank Account Number), and stores the translation from BBAN to IBAN in the TIBAN table.
So table TIBAN can have the data from two tables in SAP FICA.
1. BUT0BK - where the combination of IBAN number with Business Partner.
2. T012K - where the combination of House bank Account with IBAN number.
Hope it helps..
Thanks,
Amlan
Hi Chandra,
Have you tried to run the Z program in the target environment to recreate the quality levels at characteristic DMR as suggested by the oss note ?
Regards,
Ayoub.
Hi,
if you are using same SQL then how are you differentiating the data for mumbai & delhi?
Amit
I have a blog in preparation about using UI5 tables with Personas. I should be able to post it in the next day or two. Watch this space!
Steve.
Hi Vani
A long and prosperous career in SAP requires that we don't give up so easily.
Look through the Transport Tables directly, look at Tables E070 and E071. I doubt the Date Rule was created before the Transport system was invented
Regards
Arden