Mapping shipment idoc with XI internal structure.

Hi,
we are sending shipment idoc to PI system, there mapping is required like
for each Matnr of EIEDT43 , we need to map with EIEDL24-ARKTX with XI data type structure
where material number and Item description field is at same level but in idoc it is not.
Regards,
Mayank

for each Matnr of EIEDT43 , we need to map with EIEDL24-ARKTX with XI data type structure
where material number and Item description field is at same level but in idoc it is not
If i try to make out some sence out of your post ..it would be like you have an idoc to file scenario ,where you are trying to map a particular IDoc field under subsegments and for each occurance of the segment you need to create a field in target.
you can handle this easily if you try understanding context handeling in mapping.
http://www.riyaz.net/blog/xipi-introduction-to-context-handling-in-message-mapping/
specify your requirement clearly or frame a question.
Regards,
Anika

Similar Messages

ID : interface determination - Interface mapping (file- IDOC with externa)

Hi,
scenario : XML file read and mapped to Multiple IDOC in single message
all IR stuf are done but in the ID I cannot choose the mapping interface
here is a document of everything that was done...http://docs.google.com/Doc?id=dcsvs2n3_51jnrfw6
Thanks for the help

Hi Stepen,
Simple for Reciever Business System did you add the Idoc itself that was imported as Receiver Interface..
Just double click the Receiver Business System and Then click Receiver and See if the IDOC name exists other wise insert it...
<b>Also In</b> the Interface determinatin select the actual idoc that you imported and not the XSD....
Finally if the above doesnt work Try this since you are using ED create Message Interface and mention the xsd as MT.... and in Interface Determination use the Actual idoc imported and not ED ....
Regards,
sridhar
Message was edited by:
sridhar reddy kondam

Advanced mapping from IDOC to SOAP with reversed 3 level context change

Hi everyone.
I am having a though time mapping the HRMD_A01 IDOC into a SOAP message. The reason is that the reciever expects an xml structure where the root node is cost center instead of employee which is the case in the IDOC.
Mapping from:
IDOC (1..1)
   E1PLOGI (1..unb)
     SEGMENT (String)
     OBJID (String)
     E1PITYP (1..unb)
       E1P0001 (1..unb)
         SEGMENT (String)
         KOSTL (String)
To this structure:
List (1..1)
CostCenters (1..unb)
    KOSTL (String)   ----> Mapped against KOSTL above
    Employees (1..unb)
      OBJID (String)   ----> Mapped against OBJID above
I expect several occurances of E1PLOGI which states multiple employees sent in the IDOC. I also expect several occurences of E1P0001 containing cost centers.
My conclusion is that I need an advanced mapping and I have created one which collects all KOSTL for the IDOC context, deletes duplicates, and creates the CostCenters segment. This is now working. But my problem is that I can't create the employees segment in the right place. They are only created once under the first CostCenters node.
Here's the java-code for mapping between KOSTL and CostCenters/KOSTL:
public void costCenters(String[] var1, ResultList result, Container container) throws StreamTransformationException{
Set set = new HashSet(Arrays.asList(var1));
String[] array2 = (String[])(set.toArray(new String[set.size()]));
Arrays.sort(array2);
for (int i = 0; i < array2.length; i++) {
    result.addValue(array2<i>);
Any ideas on how to proceed?
Best Regards

Hi,
Do the mapping like below.
UDF should be select as context.
List (1..1)
CostCenters (1..unb)
    KOSTL (String)   ----> Mapped against KOSTL above
    Employees (1..unb)
      OBJID (String)   ----> Mapped against OBJID above
Mapping:
KOSTL(RightSelectChange the context to E1PITYP)--UDF--Removecontext--CostCenters
KOSTL(RightSelectChange the context to E1PITYP)--UDF--SplitbyValue(Each Value)--KOSTL
constant---Employees
OBJID----------------------------------------------Use One As Many---SplitByValue (EachValue)----------OBJID
KOSTL(RightSelectChange the context to E1PITYP)--UDF---
KOSTL(RightSelectChange the context to E1PITYP)--UDF---
Regards,
Prakasu.M
Edited by: prakasu on May 20, 2009 3:28 PM

Multi Mapping - Receiver IDOC & Mail with BPM

Hi,
Is it possible to use BPM with Multi Mapping for IDOC & Mail receivers sent parallely..
Appreciate your help ..
Thanks,
vasanth.

Hi Michal,
Thanks Michal,
We are using PI 7.1, Our Scope to do File to IDOC & Mail scenario in between we have to do RFC Lookups..
Could you pls guide me thru the steps fo BPM,
1 SA -> OB to AA
2 ID -> OB to AA & AA to Recv
3.RD -> OB to AA & AA to Recv
4.RA -> AA to IB & AA to IB
Correct me if i'm wrong..
Clarification : Is there is any way out to implement this scenario with out BPM.
We already implemented this scenario with 2 MM & 2 OM, Scenario works fine...but we have to use 1 Mapping..
Appreciate your help in advance..
Thanks,
vasanth.

Payload in String need Java mapping to IDOC structure

Hi
I have a payload in a field and that payload needs to be mapped to IDOC sturcture. As per my understanding I will have to write java mapping for the same.
I don't have any background of java, can anyone help me do this stuff or give me some inputs for the same.
Regards
Ria

Dear Ria,
Does the Source field consists of payload, then there must be original payload for which you have created Source Structure in XI right.
I think your source structure look like this if I'm not wrong:
<Data Type>
    < Field>
      <Field>
       <Field-Payload>
       </Field-Payload>
       </Field>
       </Field>
</DataType>
If this is so, you can split the values in the field by FCC. If your field consists of simple payload you can use String functions to extract the value and map it to IDOC field.
Best Regards
Praveen K

How to create an internal table with a types structure?

Hi experts,
I've 3 internal tables with the same structure, I think I could put a type structure and put that type inside the body of the internal data, is this possible? If true, how can I put that?
Example:
TYPES: Begin of type_s,
               pernr like pa0001-pernr,
             end of type_s.
Data: begin of itab_1 occurs 0,
¿¿¿??? reference to type_s
         end of itab_1.
Thanks a lot,
Regards,
Rebeca

Hi,
Use like this..
DATA: Begin of type_s,
pernr like pa0001-pernr,
end of type_s.
DATA: BEGIN OF ITAB_1 OCCURS 0.
INCLUDE STRUCTURE type_s.
DATA: END OF ITAB_1.
Otherwise like this.
types: Begin of type_s,
pernr like pa0001-pernr,
end of type_s.
Data: itab_1 type standard table of type_s.
Note: You have to create work area explicitly.
Like this
data wa like itab1.
Edited by: Velangini Showry Maria Kumar Bandanadham on May 26, 2009 1:04 PM

Mapping shipment 05 idoc

hi experts,
we have a scenario to map shipment 05 idoc to delivery 05 idoc. there will be one or more handling units in source idoc.for every handling unit in shipment 05 we should map respective article information to seperate delivery 05 idoc. this means foe every e1edl37 segement in source idoc we need to create seperate delivery05 . but the occurence of the imported delivery 05 idoc is 1. so how to map this.. do we need to go for bpm. can anyone please suggest.

Hi,
1)Double Click on the imported IDOC
2)Export the WSDL file to your desktop.
3)Change the max occurrence of the IDOC Segment.
e.g.
Original
<xsd:element name="IDOC" type="CAP_PRIMCOST.CAP_PRIMCOST01" />
Change
<xsd:element name="IDOC" type="CAP_PRIMCOST.CAP_PRIMCOST01" minOccurs="0" maxOccurs="999999999" />
4)Import the new WSDL as an external definition and use it insted of IDOC.
Regards,
Himanshu
Edited by: Himanshu Mohan on Oct 7, 2008 1:55 PM

Mapping every row to an idoc with same header

hi,
i have record:
recordset 1..1
Header 1..1
Row      0..unbounded
i want to map it to :
idoc 0...unbounded
Header 1..1
Row     1..1
i want every row in source will create an idoc. every idoc will have same header but different row.
can u please explain how do i do that?
thanks,
Tomer

Hi,
Map row node with IDOC node. It will create an IDOC per row.
Now map header node with header node. Between the header nodes you have to create a User defined function commonlly named CopyPerValue:
public Void copyPerValue (String[] a, String []b, ResultList result, Container container){
for (int i=0; i<a.length; i++){
      result.addValue(b[0]);
You have to map row with a. And header with b.
Regards,
Carlos

Mapping problem: IDOC - XI - File

Hi,
in my scenario (Z-IDOC - XI - File) I have problems with the mapping:
Z-IDOC :
ZFIBUCH1
_IDOC
___Begin
___EDI_DC40
___Z1L061 (0..999999999)
_____Z1L062 (0..999999999)
example
L061 18000 DE 0101 23236318 050605 EUR
__L062 18000 XXX XXX
__L062 18000 XX1 CCC3
L061 87000 DE 0101 050605 EUR
__L062 87000 XXX XXX
__L062 87000 XX1 XAA4
the result should look like this :
L061 18000 DE 0101 23236318 050605 EUR
L062 18000 XXX XXX
L062 18000 XX1 CCC3
L061 87000 DE 0101 050605 EUR
L062 87000 XXX XXX
L062 87000 XX1 XAA4
I tried the following (target)-data types in the mapping but nothing didnt work very well :
MT_ZIFUCH_FILE
__ row
_____L061
_______L062
or
MT_ZIFUCH_FILE
__ row
_____L061
_____L062
or
MT_ZIFUCH_FILE
_____L061
_____L062
Do I need here a BPM? Or should I use XSLT-Mapping??
Or knows somebody a easyer way?
Regards
Christoph

Hi,
As per my understanding to have a flat file struture you would require a flat structure at the target side.One similar to the second structure mentioned by you.
DT_Target
|_Header
|______L61.....segment (child of header)
|______L62.....segment (child of header)
Using the mapping we convert the idoc structure to flat structure and then use content conversion like this :
Recordset structure : L61,L62
L61.fieldSeparator = ,(for you this value should be space)
L62.fieldSeparator = ,
I have not been able to convert the Target hierarchial structure to a flat file via content conversion.
when i tried I got the values as
L61,1800,...EUR,L62,8700,......
Hope this helps,
Regards,
Sulakshana

ALE , EDI and IDOC with MM??

hii
What is ALE, EDI and IDOC in SAP??
How its linked with MM??
Explain the above things with example
Thanks

Hi!
IDOC = Intermediate Document
IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.
For more detailled information look in SAPNET under
http://service.sap.com/EDI
For exapmle in purchasing:
The IDoc message type ORDERS is used to send a purchase order to a vendor.
EDI = Electronic Data Interchange
EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.
Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).
In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.
Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:
If the partners have agreed using a special EDI standard, mapping between IDoc and the EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.
If both systems use SAP software, there is usually no need for mapping (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).
If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).
For example:
Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.
ALE = Application Link Enabling
ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).
To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.
With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:
Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.
For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.
Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types for distribution of master data are:
MATMAS (ARTMAS in retail system) for material master
CREMAS for Vendor master
INFREC for info record
SRCLST for source list
COND_A for conditions of info record
SRVMAS for service master data
Technical documentation to ALE can be found by path:
Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)
The most important Transactions for testing Idoc:
WE02 Display IDOC
WE05 IDOC list
WE19 Testing IDOCs
BD87 Status Monitor for ALE Messages (reprocess)
Notes:
456127 FAQ: Electronic Data Interchange (EDI) in Purchasing
536411 Sample scenario for ALE contract distribution (only internally released)
I hope I could help you fruther
Best regards
Erika

Hi Using IDOCs with LSM Workbench????

Hello,
I wanted to use IDOCs as one of the methods with the LSM Workbench. I am going to load the data from flat file to a transaction in CRM. I am just curious to know that how do I go forward with it. The first step of LSM Workbench is asking Message Type, Basic Type, Enhancement and structure assignment for EDIDC40. I have used other methods such as Direct input and Batch input. I have not used IDOCs with LSMW. Is it possible that you can give me the steps what we have to follow in order to set up the IDOCs and then use it with LSMW.
I will really appreciate if you can give me the steps or give a link which shows steps of LSMW with IDOCs..
Thanks much.
Warren

hi warren,
   first u have to configure the partner profile in lsmw
lsmw->settings->idoc inbound processing.
then u have to choose the basic type message type all those stuffs.if u have any enhacement u can use it or else leave it blank.
lsmw->settings->idoc inbound processing.
partner profile..
File port              IDOC_TEST
tRFC port
Partn.type             KU
Partn.number           106
Message type         ORDERS        Purchase order / or
Basic type           ORDERS05      Purchasing/Sales
enhancement blank
    tick it. Enable structure relation for EDIDC40
steps are:
Maintain object attributes
Maintain source structures
Maintain source fields
Maintain structure relations
Maintain field mapping and conversion rules
Maintain fixed values, translations, user-define
Specify files
Assign files
Read data
Display read data
Convert data
Display converted data
Start IDoc creation
Start IDoc processing
Create IDoc overview
Start IDoc post-processing
please don't forget to reward points....
regards,
murali.

BDBG IDOC with heirarchy

hi all,
i have a really wierd problem...
i am creating a idoc using BDBG... i am trying to create the IDOC with a header and detail heirarchy...
i searched a bit and found BDBP for the heirarchy configuration.
the IDOC type should seem like this:
header
|
> detail
but it seem that BDBP has not effect and the IDOC type seem like this:
header
detail
i am trying to create the heirarchy so that the mapping in XI should be easier.
could you help me please?
what am i missing?
btw,
the method function interface look like this:
TABLES
   IT_HEADER
   IT_DETAIL
   ET_RETURN
regards,
Roi Grosfeld
Edited by: Roi Grossfeld on Nov 4, 2008 10:00 AM

hi Gaurav,
this won't work as the structure of the idoc in the SAP system is different from what you suggest.
so the SAP system won't recognize the heirarchy which i define the XSD.
i want to change the heirarchy in the SAP System and when i import it to the PI i will have it and i won't need to do any changes to the XSD.
Regards,
Roi Grosfeld

Multi-Mapping in IDOC without using BPM ?

Hi ,
Please check ..
Can below given blog can be used to achive Multi-mapping in IDOC without using BPM ?
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Regards
PS

Solved .. Thx every one .
Approache Used :
1. Created mapping with Change signature on target Message type(idoc) with 1..N Occurence.
2. Operation mapping with change Occurence on Target Operation(1..Unbounded) .
3. Used same Operation mapping in Interface Determination with 0..unbounded(Multiplicity).

Error in message mapping of IDoC Invoic02

Hi,
i have imported the invoic02 idoc into PI system. i have mapped the required field os idoc with standard XSD which is imported through ED. I'm able to most of the fields with idoc and XSD. however, some of the node in xsd are repaeting.
so here the part of xsd with which i'm mapping.
(first_node)ListOfTaxSummary                      0..1
(second_parent_node)TaxSummary                   1..unboubed
(child_node) tax                                 1..1
(element)TaxAmount                                0..1
(element)TaxCategoryCoded                         0..1
here the i have mapped ListOfTaxSummary    with the idoc node E1EDS01
TaxSummary with E1EDS01
tax with E1EDS01.
i tried all possibilities with different mapping. but i'm able to get the tax node under taxsummary with the element. the problem its been repeated as E1EDS01 idoc repeats.
please help us in solving this problem.
Thanks
Kind regards,
Lalitkumar.

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

Vendor Master Creation through IDoc with Multiple Company Codes

I am trying to create vendor masters sent from a 3rd party into SAP using CREMAS05 IDoc. I have the requirement that the vendor should be created in each of 3 company codes and the vendor number is internally assigned in SAP.
I create my IDoc with the general data E1LFA1M and multiple E1LFB1M & E1LFB5M Children. When I post the IDoc using IDOC_INPUT_CREMAS which uses Call Transaction, the vendor gets created for the first company code, but the IDoc errors on the vendor extension XK01 for the next company code with the error: "Fill all required fields SAPMF02K 0111 ADDR1_DATA-NAME1".
In debugging through this, it appears that the vendor number that gets created in the first XK01 transaction does not get passed into the data for the second XK01 call and SAP tries to create a new vendor instead of extending the newly created one.
If I force the value in during debug after the initial call transaction into the variable h_lifnr, it works fine (Vendor created with multiple company codes.
Any help would be greatly appreciated.
-Larry

I cannot give you exact solution, but can guess why this is happening, below is what I believe.
I think Synchronous update is not happening in call transaction, second transaction is getting processed before the first one is saved, debugging it works fine, because we give system enough time to save while processing.
Generally in call transaction we have MODE, if we pass S - then synchronous update happens, in your case, you need to find the way to incorporate this.
Hope it helps.
Regards,
Ravi Kishore.

Mapping shipment idoc with XI internal structure.

Similar Messages

Maybe you are looking for