on 09-20-2007 7:23 AM
Hi Experts,
My scenario is Idoc to File.
Here my job is to convert the purchase order idoc into xml file.
In this there are three conditions.
converting the standard PO into xml file
(ii) converting the PO with serial number into xml file
(iii) converting the PO using serial number with subcontracting into xml file
so what I feel is I need to create one scenario and based on the condition that particular PO will convert into xml file.
Conditions:
if no condition is specified then it is standard PO first case
(ii) if field tdline ne space then it is PO with serial number second case
(iii) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
Please guide how to do this scenario.
IR:
1) how many data types I need to create
2) how many message types I need to create
3) how many message interfaces I need to create
4) how many message mappings I need to create
5) how many message interfaces I need to create
ID:
1) how many receiver determinations I need to create
2) how many interface determinations I need create
3) how many receiver agreements I need to create
And where to write the conditions at message mapping level or at receiver determination level.
Kindly provide solution to every point.
Regards,
Venkat.
Hi friends,
here is new document for IDOC TO FILE scenario..
http://jskcomput.blogspot.com/2013/08/idoc-to-file-scenario.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
solved the problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
IR
Import the IDoc.No need to create any message type/data type/message interface.
you can use the iDoc itself for these things
Receiver side.
Create the data type for File,Message type and Messsge interface.
Do the message mapping and interface mapping
Now comes the condition part.
This is what you need now
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you can use conditional routing via xpath in your receiver determination - /people/suraj.sr/blog/2006/01/05/multiple-inbound-interfaces-within-a-service
ref the above for an idea, in case u need more inputs let us know ..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venkat,
check this link,
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Samson Rodrigues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1) if no condition is specified then it is standard PO first case
2) if field tdline ne space then it is PO with serial number second case
3) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
you have to create
1. outbound ( IDOC)
2. 3 Inbound (same MT)
create 3 mapping program each for 1 condition
create 3 interface mappings
ID:
1 reveri BS.
3 Interface determinations, so 3 receiver agrement.......
you can put the condition on the mapping or in the condition tab of the interface determinations.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.