Doubt in fields - message mapping (file 2 idoc scenario)

while doing message mapping in file 2 idoc scenario, i could not able find the values for some field names
( i am following this wiki help
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC& )
cremas04 idoc
vendorNo LIFNR
vendor name Name1
Pur_org ? ( I could not able locate field with the similar desc in idoc MT side)
Company code ?
Acc_Grp ?
Search term MCOD1
Address ADRNR
City ORT01
Pin_code PSLTZ
could you help me out with this?
Message was edited by: praba
praba

hi,
I got the answer.

Similar Messages

ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

Hi,
I got this error in FIle-IDOC scenario.
ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
Is there any other suggestions?

Hi aarthi,
I suggest u chk all d settings dat u hav done..
Steps for ALE settings:-
Steps for XI
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the R3 system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto IDX1.
 Create a new port.
 Give the port name.
 Give the client number for the R3 system.
 Select the created Rfc Destination.
Step 3)
 Goto IDX2
 Create a new Meta data.
 Give the Idoc type.
 Select the created port.
Steps for R3.
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the XI system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto WE21.
 Create a port under transactional RFC.(R3->XI)
 Designate the RFC destination created in prev step.
Step 3)
 Goto SALE.
 Basic settings->Logical Systems->Define logical system.
 Create two logical systems(one for XI and the other for R3)
 Basic settings->Logical Systems->Assign logical system.
 Assign the R3 logical system to respective client.
Step 4)
 Goto WE20.
 Partner type LS.
 Create two partner profile(one for XI the other for R3).
 Give the outbound or inbound message type based on the direction.
Step 5)
 Not mandatory.
 Goto BD64.
 Click on Create model view.
 Add message type.
Step 6)
 Goto WE19
 Give the basic type and execute.
 fill in the required fields.
 Goto IDOC->edit control records.
 Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
 Click outbound processing.
Step 7)
 Go to SM58
 if there are any messages then there is some error in execution.
 Goto WE02.
 Check the status of the IDOC.
 Goto WE47.
 TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
MenoN

Message Mapping of IDOC "MATMAS.MATMAS05"

Hi!
I would like to execute the following message mapping for IDoc
MATMAS05 <--> MATMAS05.
What are the recommended fields to map?
Is the a button to automatically map the fields with the same names?
Thank you very much!
regards
Thom

Hi,
you could use the button "Map Selected Fields and Substructures if Names Are Identical"
it's explained here:
http://help.sap.com/saphelp_nw04/helpdata/en/49/1ebc6111ea2f45a9946c702b685299/frameset.htm
Or if you do it without a mapping:
simple IDoc to IDoc scenario with SAP PI
Regards
Patrick

Exceptions in file-idoc scenario

Hi Folks,
I am developing a file-idoc scenario. What are the different exceptions I would be needed to handle apart from the following two identified?
1. Mapping issue
2. Problem in posting the idoc (SAP system may be down and others)
Thank you

Hi Raja,
The errors an happen at following steps:
1. Error while picking the file:File adapter error
2. Error in mapping: error due to incorrect data, incorrect format, corrupt file etc.
3. While posting Idoc: due to Incorrect userId password, due to structure not matching, destination system being down.
Hope this helps.
Regards
Vijaya

ALE Settings For File-IDOC Scenario

Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
Bopanna

HI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1)   Create an RFC Destination to the Receiving System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select Create New button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in XI towards R/3
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Inbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Message Type and Process Code.
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
                                                                                [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM

XI is not able to archive file in file-idoc scenario

Hello friends,
I have an issue in my file->idoc scenario. When a file is placed to XI's filesystem using FTP, it is placed under xiftpuser user. Owner of all directories in this structure wher the file is placed is xiftpuser. XI is not able to archive the file because of the permissions on the archive directory. But the problem is, permissions on this directory are 775 and xiftpuser and xipadm user are in the same group. So this should work. But it doesn't. When I change permissions to 777 everything works fine.
Do you have any idea what could be wrong?
Does it matter, that xipadm user has been added to the common group with xiftpuser "later", when XI was up a long time before? Do we need to restart j2ee to take these new permissions into account?
Thank you,
Olian
Edited by: Olian Saludew on Sep 23, 2008 11:46 AM

Hi,
If archive directory Path is d:\archive
Put a '\' after it.
e.g. "D:\archive\"
It will work.
Regards,
Akshay.

How to do message mapping in IDoc or RFC to file transfer ?

Hello guys. I have a doubt. I know how to do an IDoc to file or RFC to file scenario. But how to do mapping in an Idoc to file or RFC to file scenario ? As I understand mapping is done in the sender. But IDoc or RFhas no interface as its used for SAP. So where do we need to perform mapping ?

Hi,
You dont need the Data type and message type for IDOC's, RFC's and for external definitions. so u just create one DT,MT for your File structure and you need 2 message interfaces, one for file and one for the Idoc/RFC. You can use them in your mapping program.
Regards,
Kumar.
P.S: Reward Points if Helpful!!!!!!!!!

Error in message Mapping(file to file scenario)

Hi friends,
In file to file scenario i am getting error like this while activating standard change list in IR.
Activation of the change list canceled Check result for Message Mapping MM_file2filejuly27 | URN:file2fileJuly27.com:
Starting compilation
Compilation complete
Check result for Software Component Version praba.com | PRABA.COM | 2007 | 0:
The standard error type ExchangeLogData is not defined for the namespace URN:file2fileJuly27.com
Save the software component version definition again. The object is then saved automatically
could you help me out how to correct this error?

Prabha,
You should not delete any existing standard Data types provided by SAP. ExchangeLogData and ExchangeDaultData are standard data types get created when you create new namespace.
If you have already deleted then copy them from other Namespace to your namespace. Activate your default data type first and then your objects.
Hope this will solve your problem.
Nilesh

Header Mapping in Idoc scenarios

What is the use of Header Mapping in IDOC based scenarios?

Hi,
Header maping can be used to determine the destination in the interface based upon any particular field .If the field is populated with the value then that value can be used for receiver determination to send message for example you have one file that can be mapped to any one pf the multiple IDOCs then based upon the header value you can determine the destination or the IDOC goin to be used
Ckeck this link this will help you a lot
reg:HEADER MAPPING
Check these links also
Header Mapping in File to IDoc
Header mapping while using IDoc as receiver communication
Thanks
Vikranth
Edited by: Khimavath Vikranth on May 28, 2008 9:30 PM

BPM - doubt in N:1 mapping of IDOCs

Is there any DETAILED document on Mapping multiple Idocs into a single Idoc package using BPM.My doubt is in the latter part in this process(During Receiver Determination) :
Scenario : CRM->XI->R3
We will download the CREMAS03 and then make changes in the xml so that it can hold multiple IDOCs.
and then we will be collecting the Idocs(say 3 idocs at a time)...that is, appending the IDOCS(CREMAS03) into a multiline container of type CREMAS03.
In the transformation step, the multiline container containing CREMAS03 IDOCs is transformed to IDOC PACKAGE(N:1 Mapping).
In Integration Directory,We will create 2 RECEIVER DETERMINATIONS :
1.CRM->BPM :
Receiver Service :BPM Object
Inbound Interface :CREMAS
Interface Mapping :Maps the Outbound interface (vendor_out_interface) to CREMAS(Abstract Asynchronous)
2.BPM->R3 :(I have my doubt here!)
Sender Service     : CREMAS_COLLECT_PACKAGE(BPM Object)
Outbound Interface : CREMAS_package(Abstract Async, Message is the modified Multi-CREMAS PACKAGE)
Receiver Service   : R3
Inbound Interface : CREMAS.CREMAS03
Interface Mapping : NONE (WHY is that No Interface mapping is needed ???...Please elaborate)
1.HOW will the XI engine MAP the CREMAS_package to CREMAS.CREMAS03 at the end of BPM PROCESS ?
2.In BPM we have Transformed the individual Idocs into a IDOC Package BUT then at BPM->R3 Receiver Determination WHY are we mapping the CREMAS Package into Individual CREMAS Idoc ??
3.Does the R3 receive the IDOCs as a Package OR does it receive it as individual Idocs ?And when we say a Package does it mean it will contain 1 Control record & multiple Data Records(EDID) ??
4.If the R3 receives the IDOCs as a PACKAGE, THEN How does the R3 System separate the Idocs into Individual Idocs ??
Is there any specific configuration in the partner profile at the R3 side to process A IDOC package ??.
5.Also when I compare Posting Function Module IDOC_INPUT_CREDITOR and IDOC_OUTPUT_ORDERS , It seems that IDOC_INPUT_CREDITOR    can process multiple Idocs at a time while IDOC_OUTPUT_ORDERS CAN process only ONE IDOC at a time.Am I right ?)
It would be great if someone has the patience to give a detailed reply.Looking forward to the reply !!
Thanks,
Arun.

Hi Arun,
You dont need a BPM for ur requirement. All you need to do is IDOC Message pacakages. where the IDOC are sent as a single package. here is the link to the page that details on hwo to do idoc packaging.
http://help.sap.com/saphelp_nw04/helpdata/en/99/2653429392ab53e10000000a1550b0/content.htm
you also refer to Michals weblog on IDoc pacakaging. But the approach i have jsut mentioned to you is more efficent and the one suggested by SAP. Michel was supposed to write one more weblog describing this approach.
Cheers,
Naveen

Acknowledgement - IDoc-File & File-IDoc scenario

Hi All,
   Acknowledgement is possible in case of asynchronous IDoc-XI-File scenario? If yes, how to setup?
   Same as above question for File-XI-IDoc scenario.
   In case of synchronous scenario, how to setup email with acknowledgement?
Thanks a lot in advance.
Sree

Hi Rama,
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC ->
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
(It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
I hope I have answered your query.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

File -- IDOC scenario using XI 3.0

Hi
I tried out a simple flat file to IDOC scenario using XI as the middleware and tried to post documents of type CREMAS03 on the backend R/3 system.
Now, I see that there is an IDOC number generated in the XI layer by the IDOC adapter. This IDOC number is seen under <SAP:DOCNUM>XXXXXXXXXX</SAP:DOCNUM>in the
Response-->IDOCOUTBOUND section of the pipeline in SXMB_MONI
According to SAP documentation :
To enable you to select IDocs in the target system later on, the system transfers the message GUID and the IDoc number in the ARCKEY field of the IDoc control record.
Now, I do find the XI msgid given as arckey in the control record of the Inbound in the target R/3 backend system. But I cannot find the XI IDOC number being cross referenced in the control record of the IDOC in the R/3 backend.
1.Is there a way to cross reference the IDOC number in XI with the IDOC number in the R/3 backend ( we have two different IDOC numbers, right ) i.e a IDOC number to IDOC number cross referencing in this File-->IDOC inbound into the R/3 system scenario involving XI
2. In the XI box, do we get as a part of async.reponse from the R3 system, the IDOC number that is created within the R3 system ? This would serve directly as a cross reference. Or do we have to indirectly query EDIDC table in the R/3 backend with the arckey value = msgid in XI - to retrieve the IDOC number created in the R3 backend ?
Thank you in advance for your time.

Hi,
Pls look into following link about Acknowledgement.
http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
Pls note that , you can't get/receive the Acknowledgement for Sender File Adapter. Because File System acts as an Async system. But you can get the Idoc response and you can write it into another file. For this you need to use BPM.
Hope this helps..
Regards,
Moorthy

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.

Peculiar behaviour in picking file from FTP in File-IDoc scenario

Dear XI Expert,
I have successfully completed configuration of FTP --> XI --> IDoc scenario. I have noticed a peculiar behaviour in picking the file from FTP. I placed a file on FTP and activated File Adapter with poll interval '60' secs and processing mode as 'Archive'. For the first time it has picked the file with expected behaviour and IDoc got posted to SAP successfully. But when I placed file for the second time and when refreshed the FTP directory, immediately file got archived without waiting for 60 secs. But in sxi_monitor I could not see any activity of processing this scenario. Surprise is that, file got archived in target directory. This goes on and on... without registering any activity of processing the message in Message monitoring.
In adapter monitoring it shows the message as described below:
History:
2006-05-09 22:57:25 : Processing started
2006-05-09 22:57:25 : Error: Processing interrupted due to error: FTPEx: No such file
2006-05-09 22:57:24 : Processing started
2006-05-09 22:57:24 : Error: Processing interrupted due to error: FTPEx: No such file
For your information my SAP XI system is on SP16.
Please find below the parameters of sender adapter:
Quality of service: Exactly once
Poll interval: 60 secs
Processing mode: Archive
Connect Mode: Per File Transfer
Transfer Mode: Binary
Can anybody help me out in resolving such a problem in this scenario?

Hi Jayakrishnan,
Thanks for your reply.
Once again the same problem is noticed. i.e., for the first time when file adapter is activated the file got picked, activities were logged in monitoring and IDoc got posted to destination system. For the second time when file is placed, before 60 secs got completed the file is picked and archived in the target directory. No activities in monitoring are logged.
I have tried it checking the message at adapter level, but it is showing 'No results' (even in the case of successful pick of the file for the first time, not even it is showing other file adapters).
I was not able to understand where the problem could lie?
Regards,
Suraj Kumar

CIDX Standard Message Map to IDoc

Hi,
I am looking for CIDX standard message for mapping to SHPMNT05 IDoc. I want to know the standard CIDX standard message and the repository to find such standard messages when Standard IDocs available in SAP are known.
Regards,
Suraj Kumar

Hi Michal and Shabarish,
Thanks for providing the required information. I am stuck up with a issue which is explained below.
Sample xml downloaded from http://www.cidx.org/ is different from the required message.
Sample ShipNotice xml downloaded is as follows....
<?xml version="1.0" encoding="UTF-8" ?>
- <ShipNotice>
- <Header>
- <ThisDocumentIdentifier>
<DocumentIdentifier>12345678</DocumentIdentifier>
</ThisDocumentIdentifier>
- <ThisDocumentDateTime>
<DateTime DateTimeQualifier="On">2002-04-01T20:55:13Z</DateTime>
</ThisDocumentDateTime> ......
But what is required as per the business scenario is as follows
<?xml version="1.0" encoding="UTF-8"?>
<PlannedShipment>
 <PlannedShipmentIdentifier>191919</PlannedShipmentIdentifier>
 <ShipDirection>Outbound</ShipDirection>
 <FreightTerms>Pre-Paid</FreightTerms>
 <CarrierSCAC>SEFL</CarrierSCAC>
 <FreightForwarder/>
 <EquipmentType>ODY CODE HERE</EquipmentType>
 <EquipmentNumber>TRL2096</EquipmentNumber>
 <CarrierTrackingNumber>100283534</CarrierTrackingNumber>
 <LoadList>
 <Load>
 <PlannedLoadIdentifier>125656</PlannedLoadIdentifier>
 <TransportationOrderIdentifier>1230987</TransportationOrderIdentifier>
 <Schedule>
 <ScheduledPickupDate timezone="EST">2004-03-19T15:35:00</ScheduledPickupDate>
 <RequestedDeliveryDate timezone="EST">2004-03-22T15:35:00</RequestedDeliveryDate>
 <ScheduledDeliveryDate timezone="EST">2004-03-22T15:35:00</ScheduledDeliveryDate>
 </Schedule> ..........
In this case, How should I proceed?
Kindly help me out.
Thanks & Regards,
Suraj Kumar

Doubt in fields - message mapping (file 2 idoc scenario)

Similar Messages

Maybe you are looking for