IDOC to PI to MDM

Hi,
We have scenario like IDOC to MDM
where we are sending 10000(records) IDOCS to MDM. so please let me know design concerns for this w.r.t performance, BPM and mappings and also best practices .
Questions like :
1. what is the best way to receive all these 10000 IDOCS from SAP at a time and send it to MDM.
2. What is best practises to send these IDOCS from SAP to PI.
2. Does any chance to effect PI server crashes while we process 10000 IDOCs at a time? Pls. include all best practices for this scenario?
3.What mappings should I use here? Is this multi mapping required while handling IDOC to MDM graphical mapping? Then how?
We are using SAP standard IDOC(HRMD_A) and PI is 7.0
Thanks,
Shankar

Hi,
1. what is the best way to receive all these 10000 IDOCS from SAP at a time and send it to MDM.
Not advisable to trigger 10,000 Idocs at the same time.
2. What is best practises to send these IDOCS from SAP to PI.
Might be sending batches of 300-500 IDocs will be a good idea.
2. Does any chance to effect PI server crashes while we process 10000 IDOCs at a time? Pls. include all best practices for this scenario?
Well, it completely depends on your server configuration and hardware. But as I mentioned earlier, it's not advisable to trigger that many IDocs at one-go.
3.What mappings should I use here? Is this multi mapping required while handling IDOC to MDM graphical mapping? Then how?
It depends whether there is any requirement of using Multi-Mapping. If there is no special requirement, and you just have to pass the messages through PI, then use simple graphical mapping.
Regards,
Neetesh

Similar Messages

Outbound Idoc (SAP R3 to MDM) - partner_type

I'm trying to understand the concept of partner_type KU - Customer, LI - Vendor, LS - logical system (transaction we20)
When a purchase order is created then an IDOC can be automatically generated and sent from SAP R3 to vendor (via EDI) based on partner_type LI - vendor. In this case user keys in vendor number (which is the partner) to create the purchase order.
Similarly can material creation be exchanged from SAP R3 to its partner SRM or MDM system? What would be the partner_type for this scenario? (LS !! assume partner as MDM the logical system) And how would a user key in the partner (in this scenario SRM or MDM) while creating the material in SAP R3. My understanding is partner is the key driver in message control process and sending the object (matmas) to destination. There is no place holder to mention about partner while creating the material in SAP R3.

Hi Prabhu,
>>>so here u need to have partner profile defined in LI and if for a sale order then it means u doing a transaction with a cutomer and partner profile tends to be in KU.
there is no need for that
if you have XI you can do the routing inside XI very easily
and IMHO partner profiles like vendord nad customer in the past served as routing rules
so if you have XI do everything as LS <-- much easier to maintain
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Message split - XML to IDOCs - (1:n) mapping

I have to split an incoming XML(in idoc DEBMDM format) from MDM to 2 Idocs (ADRMAS & DEBMAS).
Target message set to occurences "0:unb".
Have tested my graphical-mapping in IR and its working fine. Tested the configuration and got error in IB.
In SXMB_MONI i find the error message,
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Messages in multi-message format can only be sent to one Adapter Engine</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Read in few threads about creating a "custom adapter module"...is this right? if so.... how to proceed ?
Appreciate any help.

Ram,
Message Split using Graphical Mapping that ur using now supports adapter which are on same J2EE engine .
In ur case Ur trying to post IDOCS ( I suppose ) which is not
supported in using Graphical mapping.
U need to change the design.
-- Kavitha

Reg: MDM adapter in PI 7.1

Dear All,
My scenario is IDOC PI(7.1) MDM(7.1) .
In moni it is showing successful and when checked in Runtime workbench for MDM adapter (receiver communication channel) it is showing error as,
"Message processing failed. Cause: java.lang.Exception: JNDI name of the ra connectionFactory is not configured. Go to the directory and create a value with name 'JNDIName' and value 'deployedAdapters/<ra name>/shareable/<ra name>' as module configuration data of the module 'ModuleProcessorExitBean' "
Can anyone suggest me on this.
Regards,
Lavanya.B

Hi Rajesh,
Thanks for the reply.In the Receiver MDM Adapter, we have two things,
Processing sequence
Module Name type Module key
localejbs/ModuleProcessorExitBean Local Enterprise Bean 1 (default)
Module Configuration
Module key Parameter Name Parameter Value
Could you please explain me in detail what need to filled as this is the first time I am configuring the MDM Adapter.
Regards,
Lavanya

Succesful IDOC acknowledgements from ECC

Dear MDM gurus,
What is the best way to handle acknowledgements from ECC (INTO MDM) for inbound IDOCS from MDM (MDM->XI->ECC).
We want it such that when an IDOC gets posted into ECC succesfully,it should send an acknowledgement signal back to MDM saying that IDOC was received properly.
Thanks.

HI Mugdha,
I have a concern on the Acknowledgement (ALEAUD) Idoc. I have implemented this scenario wherein DEBMAS IDoc is posted from MDM -PI - ECC and ECC sends back the acknowldgement using ALEAUD Idoc.
However, in PI (SXMB_MONI) there is no separate message entry created for this acknowledgment. The ALEAUD acknowldgement message details is attached to the original DEBMAS message which was triggered from MDM - PI - ECC. Due to this, PI interface created is not able to read the acknowledgement message and process it to post/dump the target file onto the MDM Port.
I tried triggering and ALEAUD Idoc manually using PI - RWB which generated a separate message for ALEAUD Idoc in sxmb_moni and then my target file was created in MDM (But this is just a manual way of testing the PI interface).
Can you advice on how this concern can be dealt with?
Thanks in advance,
Elizabeth.

What is the IDOCs format

hi friends,
what is the IDOCs format?
where this IDOCs format comes into picture in SAP MDM?
which systems support this IDOCs format?
plz help me

Hi Rao,
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
Please have a look on this link for IDoC:
http://searchsap.techtarget.com/sDefinition/0,,sid21_gci852485,00.html
1. What is the IDOCs format?
Ans: XML
2. Where this IDOCs format comes into picture in SAP MDM?
Ans: Idoc are used to interchange data from R3 to any external system or vice versa. As MDM stores different masters so that master data can come from an Idoc via Exchange Infrastructure (XI) or through MDM Generic Extractor or directly via an xml and xsd of an Idoc.
When we use XI or generic extractor in between MDM and R3 then we need to store Idocs scehma in to MDM for Idoc XML.
3. Which systems support this IDOCs format?
Ans: R3, XI, and some external third party systems support Idocs. Even MDM support Idoc XSD and XML.
Rewards if useful.
BR,
Alok Sharma

Vendor IDOCs are not uploading in LFA1 table

Hi All,
We have a SAP system where Vendor IDOCS are coming from MDM through SAP PI middleware. The problem we are facing is we are not able to see all Vendors in LFA1 table.
In WE05 IDOCS are posting successfully but when we check for respective vendors in LFA1 table only few vendors are available there.
Can anybody guide us to solve this issue? Also pls let us know the process of uploading master data into table as we are very new in ABAP.
Regards,
Sarita

be open minded. SAP gives several import methods to load vendors. one of them is per IDOC.
But the vendor master IDOC does not automatically create the adress master.
And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

Best practices for initial data loads to MDM

Hi,
We need to load more than 300000 vendors from SAP into MDM production repository. Import server might take days to load that much if no error occurs.
Are there any best practices for initial loads to MDM available? What considerations must be made while doing the initial loads.
Harsha

Hello Harsh
With SP05 patch1 there is a file aggregation functionality in the import port. Is is supposed to optimize the import performance.
BTW, give me your mail address and I will send you an idoc packaging paper for MDM.
Regards,
Goekhan

Processing Customer Master in MDM into SAP

Hi,
I have a requirement where I am processing DEBMAS (Customer Master) in MDM and posting in to SAP. Can somebody give me a detailed Step-By-Step procedure to go about Posting this Inbound DEBMAS Idoc to SAP from MDM?
Thanks,
Venkat.

Hi,
Generally we CIF Customers from ECC to APO , this way all of the information is passed to APO.
and maintain this customer in ECC View V_CIFVMISD.
If it is a VMI customer then you need to put some additional info like VMI customer number on VMI tab and need to extend material to customer location.
If you are creating manually customer in APO then make sure it is assigned to model 000.
Thanks,
Pavan Verma

Splitting single idoc into multiple xml's

Hello,
My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process.
and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process

Hi Abhishek,
[quote]My requirement is such that, i need to split an custom IDoc into three xml which will be picked up by MDM, as i am new to PI 7.1 kindly guide me through the process
For this, you have to go for multimapping.
The links for it are already provided in the above posts.
and the second requirement is, i need to map the same custom IDoc into three different MDM repositories pls guide me through the process
Can you please explain this requirement further?
-Supriya.

MDM Internal number Assignment

Hi Experts,
Need your guidence on the below scenario.
1. how is the internal number assignment configuration done in MDM ( where the number is generated as soon as you save the records in the repository)
2. ECC has internal number generation for FERT Material, and i am creating a record in MDM which also has internal number generation whose number range match with the ECC number range for material type FERT. what is the configuration required to syndicate the record from MDM to ECC ( as ECC has internal number generation).
Thanks in Advance.

Hi Sandhya,
Its a difficult thing to comment why the design is like this,there is a purpose why it is made such.
Suppose you create a Material in MDM system 100010002000(say) and ECC system is defined for internal number generation.
You send the material through PI to ECC as idoc.
And torrow MDM system goes down or there is a business requirement because of which you have to create Material in ECC.
This will require huge manual intervention and possibility of error is quiet high if Number range is defined as external.
Whereas if it is Internal (as in your case) ECC takes care of the number range and the sequence.
The ALE processing of idoc does not update the status of the current number range used.You can goto MMNR to check this for Material,xkn1 for Vendor.And this is the major concern with external number generation definition in ECC.
For further detaills regarding Material number range please go through :
http://saptechsolutions.com/pdf/MaterialNumberRangesAndFormatting.pdf
Hope this helps!
Thanks,
Ravi

Problems Importing INFREC01 into MDM

Good Afternoon,
We are currently trying to import the purchasing info record IDoc 'INFREC01' into the MDM Import Manager.
However, we are having difficulties matching fields between the IDoc and the repository 'Products'.
Basically the problem is as follows:
We are trying to import the INFREC01 Idoc from SAP, via XI into MDM.
In the generated xml Idoc, there are two segments that we need to import data from:
E1EINAM : Purchasing Info Record: General Data
E1EINEM : Purchasing Info Record: Purchasing Organization Data
For some reason, the import manager brings in two segments:
INFREC01
E1EINEM
The data in INFREC01 contains the fields that we require from E1EINAM but for segment E1EINEM, there is no reference to the material, vendor or info record. Fields that could all be used to match records during import.
As a result, we are unable to perform the Match Records step in the import procedure for the segment E1EINEM i.e. match to the remote key.
We have a qualified look-up in the products repository, called "Vendor-Specific Data". When I try to import, I get the message : "Map 'Vendor-Specific Data' field to import qualifier(s)"
I would like to map the Vendor number to this field (as vendor is the non-qualifier in the look-up) but the vendor number is in the other IDoc segment (INFREC01).
How do we import the purchasing info record into MDM? Is there some way that I can clone or copy the vendor field from segment INFREC01 to E1EINEM? Or should I be using some other technique?
Thanks for any help you can offer!

Hi Jonathan,
Answer to :How do we import the purchasing info record into MDM? is
You can choose between the following types of import:
a) Interactive Import
You use the MDM Import Manager to map fields, values, and records manually before import. This method is recommended for initial loading if the Import Manager maps have to be adapted.
b)Automated ImportYou use the MDM Import Server to perform an automated import. This method is recommended for delta loading if the mapping is already complete.
I'd liek to share the process flow as well: (wrt BOM record)
Extraction from Remote System
 1. Log onto your remote system.
 2. Extract BOM data records as IDoc (BOMMAT) to SAP XI.
Within SAP you can choose tools like ALE Master Data Distribution Logistics Bill of Material Material BOM BD30
While for Interactive Import to MDM:(again wrt BOM)
 1. Start the MDM Import Manager to import the created BOMMAT XML files.
 2. Connect to your MDM repository.
 3. From the Type dropdown list choose Port.
The port serves as a central depot to collect relevant information for importing data from and exporting it to remote systems as well as for defining the file type.
Ports simplify the manual and automated handling of connection information by bundling attributes (for example direction of the data flow, XML schema, import folder, maps).
 4. Select your remote system.
 5. Select the inbound port _MDMBommat04 (client-specific).
 Do not set the Read-only flag because segments are added for pivot transformations.
 6. The Import Manager loads the map defined in the port.
Hope it will suffice to hint you,
regards,
Krutarth
PS: You can have more details @
<a href="http://help.sap.com/saphelp_mdm550/helpdata/en/43/90ed70da5621b5e10000000a1553f6/frameset.htm">This Link</a>

Conditional routing - 1 sender to 1 receiver but with multiple locations

Hello Experts,
I have a scenario where i am trying to post ALEAUD Idocs (acknowledgement Idocs) from ECC - PI - MDM.
I need these acknowledgement statuses to get updated in MDM (receiver system) for MATMAS, CREMAS and DEBMAS.
I am through till receiving the acknowledgemnts in PI. I am stuck at a point wherein I need to route MATMAS related messages to a different folder in the receiver system (MDM) wheraes messages realted to CREMAS should be routed to another folder in the same receiver system (MDM) and similar is the case with DEBMAS.
ALEAUD Idoc has an element <MESTYP> which identifies whether the acknowledment belongs to MATMAS, CREMAS or DEBMAS, but i cannot use Reciever determination for conditional routing in this case.
Will BPM help in this case? If not, kindly advice the appropriate solution.
Thanks in advance,
Elizabeth.

Have you tried using Enhanced Receiver Determination? You need to define a mapping first
ALEAUD -> ReceiverDetermiation and use this mapping in your receiver determination step
in the Integration Directory. Its fairly flexible.
SAP ABA software component version, http://sap.com/xi/XI/System, ReceiverDetermination
Edited by: Sven Buttler on Sep 14, 2010 2:38 PM

HRMD_A07 Idoc to MDM using PI

Hi Team,
We had a scenario where the HR Idoc (HRMD_A07) data is getting integrated to MDM 7.1 using PI 7.1
For example 1 Pernr is having Multiple status like Active, InActive , retire etc.., so we are getting Infotype 000 & 001 multiple times.
So how do we need to Map to target where target has only 1 structure.
Source Structure
<EPLOGI>
<E1P1TYP>
 <IT0000>
 <PERNR>
 <BEGDA>
 <ENDDA>
 </IT0000>
 <IT0001>
 <PERNR>
 <BEGDA>
 <ENDDA>
 <BUKRS>
 <PERSG>
 </IT0001>
 <IT0002>
 <PERNR>
 <BEGDA>
 <ENDDA>
 <ENAME>
 <ANRED>
 </IT002>
 <IT1000> </IT1000>
</EPLOGI>
Target Structure to MDM
<Record>
<EmpNo>
<Status>
<Last_Name>
<First_Name>
</Record>
Here when we execute 2 perner's (10004300, 10004435) IDOC is getting created we are getting source structure as follows
<EPLOGI>
<E1P1TYP>
 <IT0000>
 <PERNR>10004435</PERNR>
 <BEGDA>
 <ENDDA>
 <STAT2>3</STAT2>
 </IT0000>
 <IT0001>
 <PERNR>10004435</PERNR>
 <BEGDA>
 <ENDDA>
 <BUKRS>1030</BUKRS>
 <PERSG>10</PERSG>
 </IT0001>
 <IT0002>
 <PERNR>
 <BEGDA>
 <ENDDA>
 <ENAME>xxx</ENAME>
 <ANRED>1</ANRED>
 </IT002>
 <IT1000> </IT1000>
</EPLOGI>
<EPLOGI>
<E1P1TYP>
 <IT0000>
 <PERNR>10004300</PERNR>
 <BEGDA>
 <ENDDA>
 <STAT2>2</STAT2>
 </IT0000>
 <IT0000>
 <PERNR>10004300 </PERNR>
 <BEGDA>
 <ENDDA>
 <STAT2>3</STAT2>
 </IT0000>
 <IT0001>
 <PERNR>10004300 </PERNR>
 <BEGDA>
 <ENDDA>
 <BUKRS>1030</BUKRS>
 <PERSG>10</PERSG>
 </IT0001>
 <IT0001>
 <PERNR>10004300 </PERNR>
 <BEGDA>
 <ENDDA>
 <BUKRS>1030</BUKRS>
 <PERSG>12</PERSG>
 </IT0001>
 <IT0002>
 <PERNR>
 <BEGDA>
 <ENDDA>
 <ENAME>yyy</ENAME>
 <ANRED>2</ANRED>
 </IT002>
 <IT1000> </IT1000>
</EPLOGI>
The Output target Structure should be as follows...
<Record>
<EmpNo>10004435</EmpNo>
<Status>3</Status>
<Last_Name>xxx</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
I had done an message Mapping as follows.
IT0001 ==> Record
PERNR ==> Empno
STAT2 ==> Status
ENAME ==> Last_Name
As per the mapping I m getting Output Structure as follows
<Record>
<EmpNo>10004435</EmpNo>
<Status>3</Status>
<Last_Name>xxx</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
<Last_Name>
<First_Name>
</Record>
There are some values missing in target for the Record <EmpNo>10004300</EmpNo> since the Infotype IT0002 is not repeated. Some Infotypes are not getting repeated, so the values are not getting mapped to target like Last_Name, First_Name etc...
but how do we solve it by using message mapping, Can we use any Java UDF or XSLT Mapping for this issue.
the problem in brief is some infotypes in source is getting multiple times and some are getting only 1 time.
Please suggest.
Thanks in Advance,
Sriram

Hi Raj,
The Mapping is working fine for a single Employee details, In the above target you can see the output correct for
<Empno>10004435</Empno>
If an Employee has multiple status then we are getting multiple Values of same infotype(Segments) like 2 IT000 & IT001, but for some infotype in the same IDOC we are not getting Infotype IT002, so for that record we are not getting the values in output.
For Example if an Employee has only Active status then that Employee will have only 1 action so he will only have 1 IT000,IT001 etc.. then for that record we will get the output correct.
For this Input
<EPLOGI>
<E1P1TYP>
<IT0000>
<PERNR>10004435</PERNR>
<BEGDA>
<ENDDA>
<STAT2>3</STAT2>
</IT0000>
<IT0001>
<PERNR>10004435</PERNR>
<BEGDA>
<ENDDA>
<BUKRS>1030</BUKRS>
<PERSG>10</PERSG>
</IT0001>
<IT0002>
<PERNR>
<BEGDA>
<ENDDA>
<ENAME>xxx</ENAME>
<ANRED>1</ANRED>
</IT002>
<IT1000> </IT1000>
</EPLOGI>
The Output is as follows which is correct.
<Record>
<EmpNo>10004435</EmpNo>
<Status>3</Status>
<Last_Name>xxx</Last_Name>
<First_Name>
</Record>
If an Employee has status Active and Withdrawn status then he will have 2 actions and so he will have 2 IT000, IT001 segments. For this Example see the input structure
<EPLOGI>
<E1P1TYP>
<IT0000>
<PERNR>10004300</PERNR>
<BEGDA>
<ENDDA>
<STAT2>2</STAT2>
</IT0000>
<IT0000>
<PERNR>10004300 </PERNR>
<BEGDA>
<ENDDA>
<STAT2>3</STAT2>
</IT0000>
<IT0001>
<PERNR>10004300 </PERNR>
<BEGDA>
<ENDDA>
<BUKRS>1030</BUKRS>
<PERSG>10</PERSG>
</IT0001>
<IT0001>
<PERNR>10004300 </PERNR>
<BEGDA>
<ENDDA>
<BUKRS>1030</BUKRS>
<PERSG>12</PERSG>
</IT0001>
<IT0002>
<PERNR>
<BEGDA>
<ENDDA>
<ENAME>yyy</ENAME>
<ANRED>2</ANRED>
</IT002>
<IT1000> </IT1000>
</EPLOGI>
See the Output of this above input
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
</Last_Name>
</First_Name>
</Record>
The First Segments are getting mapped correctly to Output. but the second segments are only not getting mapped since some values in Infotype or segment IT002 are missing, Means the Output till this record is correct
<Record>
<EmpNo>10004300</EmpNo>
<Status>2</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
But the second record for the same employee is missing.
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
</Last_Name>
</First_Name>
</Record>
in the above output we are missing </Last_Name>,</First_Name> etc where according to business it should be
<Record>
<EmpNo>10004300</EmpNo>
<Status>3</Status>
<Last_Name>yyy</Last_Name>
<First_Name>
</Record>
as per business we need to use the previous IT002 data of the same employee in previous action.
How can we get the previous action details in message mapping.
Thanks in Advance,
Sriram

XI Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Generated ADRMAS IDOC is
 <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
 <IDOC BEGIN="1">
 
 <EDI_DC40 SEGMENT="1"/>
 <xsl:apply-templates select="."/>
 </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

IDOC to PI to MDM

Similar Messages

Maybe you are looking for