on 03-20-2008 3:54 AM
File to Server Proxy(SAP Standard).
I have set up SRM SUS XI Content out of the box from SAP as is(SAP standard).The systems are defined in XI SLD
and the set up is running fine.SUS to SRM PO Confirmation message is working fine.
I am working on Interface which is not SAP Standard XI Content but would like to map
to the Standard Inbound ABAP Proxy from a file(ABAP proxy is SAP Standard for SRM).Some of my questions are
still answered.
Scenario:Process PO Confirmation in SRM from file from third party system(System A)
System A(sender):Will send the file in the following 855 IDOC format.
Sender file:
EDI_DC 100 ORDERS012SAPPRD KUXXX_EDI
E2EDK01 100 E2EDK01 00
E2EDK02 100 E2EDK02 001100656282
E2EDP01 100 E2EDP01 00001IP 1
E2EDP20 100 E2EDP20 1
E2EDP19 100 E2EDP19 001767950
E2EDP19 100 E2EDP19 002K006205WBB
EDI_DC 100 ORDERS012SAPPRD KUXXX_EDI
E2EDK01 100 E2EDK01 00
E2EDK02 100 E2EDK02 001100656283
E2EDP01 100 E2EDP01 00001IP 1
E2EDP20 100 E2EDP20 1
E2EDP19 100 E2EDP19 001767950
E2EDP19 100 E2EDP19 002K006205WBB
System B which is SRM( receiver )should process the above file.
XI Content on SRM has the following
Receiver Interface:"PurchaseOrderConfirmation_In"
Data: Type for receiver:"PurchaseOrderMessage"
Question1:
I am not able to map the Source message inside sap name space .Inside XI I am not abot to create a a data type or message type and do message mapping from source file to target message(PurchaseOrderConfirmation).
Even if i check the box as "Objects are modifible" on SAP Software Component ,the system gives a error message.
Is it possible to create a name space in the standard sap name space and do configure my source message(from file).
Question2:
Now I have created my own name space and copied the sap message and all sap data types into my name space.
Now how to create a data type for the above sender file and map the file contents to the target message which is
abap proxy interface."PurchaseOrderConfirmation".As inside the idoc file the occurance is more than one PO
Can I create IDOC type ORDRSP.ORDERS05 as source data type and if yes how to read the file contents to target data structure?
Question 3:
As I have created my own name space in XI ,in the SRM system using the t-code SPROXY I am trying to create the
proxy(Inbound Interface) same as sap standard proxy.So I copied the code in the method of standard proxy (which is calling standard sap function module).Now will my new proxy created if mapped in XI from above will work fine?
Thank you very much for your patience in reading this post ,I really appreciate your valuable inputs.
1. Create ur own SWC in SLD. Use "Usage Dependency" and assign the Standard SWC as dependent on ur SWC. After importing ur SWC in IR, u ll be able to see the standard components under Basis objects. Then it will support custom developments and reusability
2. For the sender file, use file content conversion or ur custom module
Direct use of Idoc structure wont work
3. Once u have followed the above steps, regenerate the proxy and it should work
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
File to Server Proxy(SAP Standard).
I have set up SRM SUS XI Content out of the box from SAP as is(SAP standard).The systems are defined in XI SLD
and the set up is running fine.SUS to SRM PO Confirmation message is working fine.
I am working on Interface which is not SAP Standard XI Content but would like to map
to the Standard Inbound ABAP Proxy from a file(ABAP proxy is SAP Standard for SRM).Some of my questions are
still answered.
Scenario:Process PO Confirmation in SRM from file from third party system(System A)
System A(sender):Will send the file in the following 855 IDOC format.
Sender file:
EDI_DC 100 ORDERS012SAPPRD KUXXX_EDI
E2EDK01 100 E2EDK01 00
E2EDK02 100 E2EDK02 001100656282
E2EDP01 100 E2EDP01 00001IP 1
E2EDP20 100 E2EDP20 1
E2EDP19 100 E2EDP19 001767950
E2EDP19 100 E2EDP19 002K006205WBB
EDI_DC 100 ORDERS012SAPPRD KUXXX_EDI
E2EDK01 100 E2EDK01 00
E2EDK02 100 E2EDK02 001100656283
E2EDP01 100 E2EDP01 00001IP 1
E2EDP20 100 E2EDP20 1
E2EDP19 100 E2EDP19 001767950
E2EDP19 100 E2EDP19 002K006205WBB
System B which is SRM( receiver )should process the above file.
XI Content on SRM has the following
Receiver Interface:"PurchaseOrderConfirmation_In"
Data: Type for receiver:"PurchaseOrderMessage"
Question1:
I am not able to map the Source message inside sap name space .Inside XI I am not abot to create a a data type or message type and do message mapping from source file to target message(PurchaseOrderConfirmation).
Even if i check the box as "Objects are modifible" on SAP Software Component ,the system gives a error message.
Is it possible to create a name space in the standard sap name space and do configure my source message(from file) so that
I can make use of sap standard proxy from the sap name space
Question2:
Now I have created my own name space and copied the sap message and all sap data types into my name space.
Now how to create a data type for the above sender file and map the file contents to the target message which is
abap proxy interface."PurchaseOrderConfirmation".As inside the idoc file the occurance is more than one PO
Can I create IDOC type ORDRSP.ORDERS05 as source data type and if yes how to read the file contents to target data structure?
Question 3:
As I have created my own name space in XI ,in the SRM system using the t-code SPROXY I am trying to create the
proxy(Inbound Interface) same as sap standard proxy.So I copied the code in the method of standard proxy (which is calling standard sap function module).Now will my new proxy created if mapped in XI from above will work fine?
Thank you very much for your patience in reading this post ,I really appreciate your valuable inputs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.