2007 Feb 19 11:06 AM
Hi all,
We have two different SAP systems (call it system A and system B). The vendor data is created and updated in system A and CREMAS idoc is generated to pass the data to system B.
The problem come since the system B have some fields as display (the update has to be only possible from system A) that in system A are mandatory. The funtion that process the Idoc finally use a call transaction to XK02 so the fields are not updated in system B with the info sent from system A.
Could you help me to find some workarround to solve this situation?
Thanks in advance.
Regards.
Mensaje editado por:
Francisco Asensio
2007 Feb 19 3:04 PM
Hello Francisco,
I have faced a similar problem in other functional areas.
What I did was talk to the functional/Configuration team and find out if these fields are really needed to reflect the same data as system A and then have them change the display only fields to update mode.
This sounds very simple but it is possible that the configuration team did not consider ththis when they kept the fields display only in one system and not the other.
Maybe you are looking for a technical reason but I feel you should try this approach.
Regards
Hi all,
We have two different SAP systems (call it system A and system B). The vendor data is created and updated in system A and CREMAS idoc is generated to pass the data to system B.
The problem come since the system B have some fields as display (the update has to be only possible from system A) that in system A are mandatory. The funtion that process the Idoc finally use a call transaction to XK02 so the fields are not updated in system B with the info sent from system A.
Could you help me to find some workarround to solve this situation?
Thanks in advance.
Regards.
Mensaje editado por:
Francisco Asensio
2007 Feb 19 3:04 PM
Hello Francisco,
I have faced a similar problem in other functional areas.
What I did was talk to the functional/Configuration team and find out if these fields are really needed to reflect the same data as system A and then have them change the display only fields to update mode.
This sounds very simple but it is possible that the configuration team did not consider ththis when they kept the fields display only in one system and not the other.
Maybe you are looking for a technical reason but I feel you should try this approach.
Regards
2007 Feb 19 3:25 PM
Hi Sandeep.
Thanks for your answer.
I have already try to convince confiruration team to open this fields to modify, but they do not take that as a posibility.
Regards,
2007 Feb 19 3:40 PM
ok, in that case you need to find a fucntion/BAPI which does not use a call transaction.
Call transactions will be afftected by the display only status of a field, but a BAPI should be able to do this .
Regards
2007 Feb 19 3:47 PM
You are rigth, the problem is that I have already not found it for Vendors (I have found some, but only for online update), but I still looking for.
Thanks a lot for your answers.
Regards,
2007 Feb 19 3:50 PM
Hi,
You can use this BAPI BAPI_VENDOR_EDIT or FM VENDOR_UPDATE to update vendor.
Regards,
Ferry Lianto
2007 Feb 19 4:08 PM
Hi Ferry.
I had already look the BAPI, but unfortunately this one, at the end, only make a call transaction to XK02, so the problem persist.
I will look on the FM now.
Thanks for your help.
Regards,
2007 Feb 22 11:08 AM
Hi all,
This FM looks that do not make any check and update all fields (even that I don not want to). So finally I look for other one or make the update directly in the tables (crosing finger)....
Thanks all for your help.
Regards
2007 Feb 22 3:03 PM
Francisco, yes sometimes one has to update the tables directly.
But remember , one field in a transaction may be updating that field in a lot of tables.
So be careful with that, do a thorough research.
Good Luck.
Regards
2007 Feb 22 3:16 PM
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |