Inbound Idoc Data mapping sheet

Hi experts,
I need a data mapping sheet of Inbound Idoc that will help me for mapping the segments (header, Item) both for creating material, vendor, customer etc.
That sheet will help for mapping tables and fields that are mandatory for that segments.
Thanks & Regards.
Ankur Garg.

The process code you assigned to the inbound IDoc, has to be assigned to a function module which processes this IDoc, right? Now, if you use a function module of your own (CUSTOM FM!), you can do all the 'printing' you want.
So there is no option for printing by default (standard), but you will have to do it your self.
Another option would be to use a User exit. It seems there is a standard User exit (SIDOC001), or even a BAdI which you can use. I haven't used it myself, so can't help you there.
Edited by: Micky Oestreich on Mar 9, 2009 8:43 AM

Similar Messages

Data Mapping Sheet/ Data Mapping Form

Dear Forum Members
Can anyone provide example data mapping sheets or forms. And/or documents prepared during the conversion process
thanks
Any help will be appreciated
my yahoo id is o2dataone

Hi Cet,
If you need all the information from one table i think this is going to be difficult
Based on the BW Types you can put a selection in the TADIR table and get the entries in the Bw side.
After fetching the different Infoprovider names you need to make use of different tables such as
RSDODSO
RSDCUBE
RSIO etc and you can make a vlookupin your excel to fetch the necessary information from the different Excel sheet tables that you have downloaded.
Just a suggestion
Prathish

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

Inbound Idoc - Date fields not getting saved

Hello,
I have created inbound idoc scenario in SAP. I receive Idoc from non SAP system to SAP system.
then data from IDoc is saved into different tables, for that I have written one function module (attached to process code)
One of the segments in IDoc type has date as a field. It is of type sy-datum.
When I receive Idoc in SAP only date fields are not getting saved in tables.
Is anything specific need to be done for date fields? please advice.

check which format you are getting into sap and make sure you are coverting in into required format.

Invoice IDOC data mapping

plz help in mapping of these two fields in INVOIC02 IDOC
BSCHL Posting Key
GJAHR Fiscal year
thanks ..
plz send me if you have any info about data mapping and processing a idoc...
pts ll be given to all helpful answers
Message was edited by: sharadha sharma

INVOIC02 is for billing document. If you are looking for accounting document then i think you should be looking at ACC_DOCUMENT02.

Inbound IDOC data printing

Hi All,
I have created one inbound zIDOC, which have structure containing three headers and one text segement.
Now I want to print the data of this inbound idoc as soon as it is trigrred , can any body have any idea of any FM that can be used ?
Looking for your valuable input.
Regards
Ajay

The process code you assigned to the inbound IDoc, has to be assigned to a function module which processes this IDoc, right? Now, if you use a function module of your own (CUSTOM FM!), you can do all the 'printing' you want.
So there is no option for printing by default (standard), but you will have to do it your self.
Another option would be to use a User exit. It seems there is a standard User exit (SIDOC001), or even a BAdI which you can use. I haven't used it myself, so can't help you there.
Edited by: Micky Oestreich on Mar 9, 2009 8:43 AM

Reg : IDOC data mapping

Hi All,
Which is the function module which Extracts the data from the application document ( Sales order or quotes ) and populates to the SAP message type Idoc segments.
what are the SAP table involved in doing this mapping.
Thanks & Regards.
vijay

Unfortunately the mapping is not in any table but in the source code as extracted here:
e1cuins-class_type        cuins-class_type
e1cuins-inst_id           cuins-inst_id
e1cuins-obj_key           cuins-obj_key
e1cuins-obj_txt           cuins-obj_txt
e1cuins-obj_type          cuins-obj_type
e1cuins-quantity          cuins-quantity
e1cuprt-class_type        cuprt-class_type
e1cuprt-inst_id           cuprt-inst_id
e1cuprt-obj_key           cuprt-obj_key
e1cuprt-obj_type          cuprt-obj_type
e1cuprt-parent_id         cuprt-parent_id
e1cuprt-part_of_no        cuprt-part_of_no
e1cuval-author            cuval-author
e1cuval-charc             cuval-charc
e1cuval-charc_txt         cuval-charc_txt
e1cuval-inst_id           cuval-inst_id
e1cuval-value             cuval-value
e1cuval-value_txt         cuval-value_txt
e1edk01-autlf             xvbak-autlf
e1edk01-belnr             ekko-ebeln
e1edk01-bsart             ekko-bsart
e1edk01-curcy             iso_waers
e1edk01-kzabs             pekko-kzabs
e1edk01-kzazu             xvbkd-kzazu
e1edk01-lifsk             xvbak-lifsk
e1edk01-recipnt_no        ekko-lifnr
e1edk01-vsart             xvbak-vsbed
e1edk01-zterm             ekko-zterm
e1edk02-belnr             ekko-angnr
e1edk02-belnr             ekko-ebeln
e1edk02-belnr             ekko-konnr
e1edk02-belnr             ekko-submi
e1edk02-belnr             pekko-labnr
e1edk02-datum             ekko-bedat
e1edk02-uzeit             sy-uzeit
e1edk03-datum             ekko-angdt
e1edk03-datum             ekko-bedat
e1edk03-datum             ekko-bnddt
e1edk03-datum             ekko-bwbdt
e1edk03-datum             ekko-ihran
e1edk03-datum             ekko-kdatb
e1edk03-datum             ekko-kdate
e1edk03-datum             pekko-eindt
e1edk03-datum             sy-datlo
e1edk14-orgid             ekko-bsart
e1edk14-orgid             ekko-bukrs
e1edk14-orgid             ekko-ekgrp
e1edk14-orgid             ekko-ekorg
e1edk17-lkond             ekko-inco1
e1edk17-lkond             xvbkd-inco1
e1edk17-lktext            ekko-inco2
e1edk17-lktext            xvbkd-inco2
e1edk18-prznt             ekko-zbd1p
e1edk18-prznt             ekko-zbd2p
e1edk18-tage              ekko-zbd1t
e1edk18-tage              ekko-zbd2t
e1edk18-tage              ekko-zbd3t
e1edka1-bname             ekko-verkf
e1edka1-bname             t024-eknam
e1edka1-ihrez             ekko-ihrez
e1edka1-ihrez             ekko-unsez
e1edka1-ilnnr             h_iln_vendor
e1edka1-lifnr             h_pekko_werks
e1edka1-lifnr             pekko-werks
e1edka1-orgtx             t024e-ekotx
e1edka1-pagru             ekko-ekgrp
e1edka1-paorg             ekko-ekorg
e1edka1-partn             ekko-lifnr
e1edka1-partn             ekko-logsy
e1edka1-partn             lfa1-lifnr
e1edka1-partn             lfb1-eikto
e1edka1-partn             pekko-kunnr
e1edka1-partn             t000-logsys
e1edka1-partn             xvbpa_we-kunnr
e1edka1-parvw             'EZ'
e1edka1-parvw             h_parvw
e1edka1-parvw             'LF'
e1edka1-parvw             'WE'
e1edka1-spras             ekko-spras
e1edka1-telf1             ekko-telf1
e1edka1-telf1             t024-ektel
e1edka1-telfx             t024-telfx
e1edkd1-ekgrp             ekko-ekgrp
e1edkd1-ekorg             ekko-ekorg
e1edkp1-defpa             xekpa-defpa
e1edkp1-ekorg             xekpa-ekorg
e1edkp1-lifn2             xekpa-lifn2
e1edkp1-ltsnr             xekpa-ltsnr
e1edkp1-parvw             xekpa-parvw
e1edkp1-werks             xekpa-werks
e1edkt1-tdid              xt166a_del-tdid
e1edkt1-tdid              xt166k_del-tdid
e1edkt1-tsspras           ekko-spras
e1edp01-abftz             ekpo-abftz
e1edp01-antlf             xvbap-antlf
e1edp01-bmng2             ekpo-ktmng
e1edp01-bmng2             ekpo-menge
e1edp01-bpumn             ekpo-bpumn
e1edp01-bpumz             ekpo-bpumz
e1edp01-brgew             e1edp01-menge*ekpo-brgew
e1edp01-evers             ekpo-evers
e1edp01-gewei             ekpo-gewei
e1edp01-kzabs             ekpo-kzabs
e1edp01-lgort             ekpo-lgort
e1edp01-matkl             ekpo-matkl
e1edp01-matnr             ekpo-matnr
e1edp01-menee             ekpo-meins
e1edp01-menge             ekpo-ktmng
e1edp01-menge             ekpo-menge
e1edp01-netwr             ekpo-netwr*cur_factor
e1edp01-ntgew             e1edp01-menge*ekpo-ntgew
e1edp01-peinh             ekpo-peinh
e1edp01-pmene             ekpo-bprme
e1edp01-posex             ekpo-ebelp
e1edp01-posguid           xvbap-posguid
e1edp01-pstyp             ekpo-pstyp
e1edp01-uepos             ekpo-uebpo
e1edp01-vprei             ekpo-netpr*cur_factor
e1edp01-werks             ekpo-werks
e1edp02-belnr             ekpo-aktnr
e1edp02-belnr             ekpo-konnr
e1edp02-belnr             ekpo-labnr
e1edp02-belnr             h_xvbkd-bstkd_e
e1edp02-belnr             xvbap-werks_ext
e1edp02-belnr             xvbkd-bstkd_e
e1edp02-bsark             h_xvbkd-bsark_e
e1edp02-bsark             xvbkd-bsark_e
e1edp02-ihrez             h_xvbkd-ihrez_e
e1edp02-ihrez             xvbkd-ihrez_e
e1edp02-zeile             ekpo-ktpnr
e1edp02-zeile             h_xvbkd-posex_e
e1edp02-zeile             xvbkd-posex_e
e1edp03-datum             ekpo-abdat
e1edp03-datum             ekpo-agdat
e1edp17-lkond             ekpo-inco1
e1edp17-lkond             xvbkd-inco1
e1edp17-lktext            ekpo-inco2
e1edp17-lktext            xvbkd-inco2
e1edp19-idtnr             ekpo-ematn
e1edp19-idtnr             ekpo-idnlf
e1edp19-idtnr             ekpo-matnr
e1edp19-ktext             ekpo-txz01
e1edp20-ameng             xeket-ameng
e1edp20-ameng             xeket-wemng
e1edp20-edatu             xeket-eindt
e1edp20-ezeit             xeket-uzeit
e1edp20-wmeng             xeket-menge
e1edpa1-partn             ekpo-kunnr
e1edpa1-partn             xvbpa_we-kunnr
e1edpd1-bednr             xekpo-bednr
e1edpd1-bstae             xekpo-bstae
e1edpd1-insmk             xekpo-insmk
e1edpd1-knttp             xekpo-knttp
e1edpd1-kzabs             xekpo-kzabs
e1edpd1-labnr             xekpo-labnr
e1edpd1-lgort             xekpo-lgort
e1edpd1-mahn1             xekpo-mahn1
e1edpd1-mahn2             xekpo-mahn2
e1edpd1-mahn3             xekpo-mahn3
e1edpd1-mwskz             xekpo-mwskz
e1edpd1-prsdr             xekpo-prsdr
e1edpd1-schpr             xekpo-schpr
e1edpd1-spinf             xekpo-spinf
e1edpd1-uebtk             xekpo-uebtk
e1edpd1-uebto             xekpo-uebto
e1edpd1-untto             xekpo-untto
e1edpd1-webre             xekpo-webre
e1edpd1-werks             xekpo-werks
e1edpt1-tdid              xt166p_del-tdid
e1edpt1-tsspras           ekko-spras
e1eds01-summe             ekko-ktwrt*cur_factor
e1eds01-summe             pekko-netwr*cur_factor
e1eds01-sunit             iso_waers
Whenever you have qualifiers, the segments appear multiple with diefferent fields.
Regards,
Clemens

INVOIC02 IDoc - data mapping

Does the following attributes exist in the standard INVOIC02 Idoc:
Contract Date
Contract Type
Delivery Date
Shipping Point
Shipping Condintion
Transport Method
Thanks,
Faisal

Please check for the fields in IDOC documentation using Transaction WE60.
Thanks.

Inbound Idoc with T-code: BORGR ( Inbound delivery create) EDI cannection

Dear all,
Kindly help me to create inbound delivery with BORGR transaction.
Here the we have to create the inbound delivery in the system with the help of vendor number and material without using Scheduling agreement number in BORGR
Please suggest the processing code and the function module required for the BORGR document posting.
I have done the following steps u2026but not able to post the dummy idoc through WE19 .
1. Use standard message Type DESADV (T code: WE81).
2. Use standard IDOC type DELVRY05 (T code: WE30).
3. Assign message type to IDOC Type ( Tcode: WE82).Message Type:-DESADV, Basic Type:-DELVRY05,Release 700
4. Use standard assignment of process code DELS with the message type DESADV ( Tcode: WE42)
5. Inbound Function Module : IDOC_INPUT_DESADV1 ( T code : WE57)
6. Define Port type File (Tcode: WE21) Port u2013 EDI_ASN Inbound Delivery.
7. Define Partner Profile (Tcode: WE20) Inbound Parameters.
8. Enhancement can be done in inbound IDOC as per the business requirement. Business has confirmed Field name wise Inbound IDOC data which will be received from vendor and all fields are available in the standard IDOC type DELVRY05.
Please help if anything more required for posting dummy idoc .
Thanks and regards,
koshti

Hi Dick,
just one additional hint as we had recently such problems :
It my happen that DESADV creates an inb.del w/o packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
Kind Regards
Kay

Data mapping

Hi guys,
what is data mapping? I don't think this is XI mappings.is this something related to EDI
Thanks
Sud

Sud,
It all depends on the context where u are using these terms. As per the XI Mappings there is nothing like data mapping.
In my client place they will call the Transformation document as Data Mapping sheet. It's nothing but the data mapping between the source and the target structure. I mean how the source structure need's to be transformed to the target will be defined in the data mapping sheet.
raj.

Retrigger an Inbound IDoc to Become an Outbound from PoSDM to ECC

Dear PoSDM Experts,
I'm trying to browse and search for solutions on whether retriggering the inbound IDoc to an outbound IDoc from PoSDM to ECC without changing its details and had no luck. The scenario has no aggregation and it is merely passing through PoSDM. I understand it doesn't seem practical because we can point the IDoc directly to ECC without passing PoSDM. The full scenario is an inbound IDoc is created in PoSDM coming from PI and the same IDoc will be triggered and pushed to ECC without changing the details. Sample IDoc would be WPUUMS, WPUBON and WPUTAB.
Please let me know if the above scenario is possible without enhancement. If it is possible, kindly provide me how I should execute it in PoSDM.
Kind regards,
Mark

Hi Mark,
Well if that is the case then I will suggest you to go with custom development.
Create Z tables for storing Inbound IDoc data in POS DM.
Write FM to process your inbound IDocs in POS DM Z tables.
Write FM to generate your outbound IDocs from POS DM Z tables.
Thanks,
Vikrant.

MASTER_IDOC_DISTRIBUTE inbound idocs?

I am trying to post an inbound IDOC that was created inside an ABAP program.
I have tried MASTER_IDOC_DISTRIBUTE and set the direction on the control record to '2' (inbound), however when i look at the idoc posted in WE02, its in the outbound section, not the inbound. Of course it's failing there because the partner is not set up (nor should it be) to process this idoc as outbound.

Hi, I think if you direcly call this FM (IDOC_INPUT_ORDERS), it can goes, even without the IDOC number. The IDOC number is for the EDI/ALE layer to differentiate the IDOCs, but it looks no usage in the Inbound FM inside, as these FM is only for inbound IDOC data into server.
Maybe there will be some consistency issue occur, but the inbound can be done, haven't tried it.
By the way, it looks you want to create a IDOC which has the same sender and receiver, it has some other way, you can reference in the following link:
http://www.sapgenie.com/ale/whitepaper.htm
In The 7.3 Topic it has been explained to configure this scenerio.
hope it will be helpful
Thanks a lot

INBOUND IDOC REPROCESSING IN CUSTOM PROGRAM

Hello,
I have a custom program which displays the INBOUND IDoc data for the message type = ZSTLSP in the ALV format.
Requiremt is that I shall select a record and change one of the coulmn contents . A button 'Reprocess' will be
made available , when clicked it needs to reprocess the Idoc . The reprocessed idoc will be strored with the new values entered
and the original idoc will be stored with status 70.
Kindly let me know how to reporcess the IDoc in the custom program.
Note that If I try to cakk l standard program RBDAPP01 to reprocess the IDOCs using SUBMIT statement. We can pass the IDOC Number, Message type etc. while submitting the program but CANNNT pass the changed SDATA field.
Thanks in Advance!!
Senthil

I am able to change the value using FM IDOC_INPUT , but the changed values is not updateing in the databse.
Maybe I need to do commit. kindly let me know how to do commit in this scenario.
Senthil

Some Data Missing in the inbound Idoc received from Gentran

Hi,
We are receing one custom message type with the basic type ORDER05 in SAP from Gentran. When we checked the destination file generated in Gentran, its showing data for all the segments. However in SAP when we checked the corresponding idoc we find the segment E1EDP05 is missing. The Gentran team says they are placing the destination file in the unix server of SAP. However we dont find these files in the SAP Unix server. Could anybody advise what could be the problem and where we need to check further ?

Gentran will never be able to create an IDOC within SAP. Here is what happens:
> Gentran creates a flatfile/XML which is in the IDOC format (the one which you can see in WE60).
> Gentran then places this flat file/XML in a folder on Application server. This can be UNIX, Windows NT, etc..
> Gentran then triggers the Startrfc.exe which will trigger EDI_DATA_INCOMING function module.
> This FM will parse the data, check it for consistency of the defined standards, then write the control record into EDIDC and corresponding data records into EDID4 and updates the relevant statuses (i.e. 01 - added, etc). It'll then look into the partner profile setup, look for process code and moves the status to 64 and calls the inbound FM which will post the application document.
In you case, you need to find out what file is coming in and where E1EDP05 has missed. The data will only be sent by Gentran. The inbound function modules will never update IDOC data records (unless there is a customization). The status records are updated.
If E1EDP05 is not mapped and sent by Gentran and you still used to see it, then there should have been a customization in place to add values to IDOC segment fields. Try to get the final file that is mapped from either X12/EDIFACT and then see if E1EDP05 segment is present in there. If it is present then upload the same file into AL11 using CG3Z and call EDI_DATA_INCOMING or WE19 to process it. Once processed, you'll can observe if E1EDP05 is being created or not.

Mapping for INBOUND sales data

Hi All, I am working on SAP-POS integration for a retailer. My question is on mapping of inbound sales data with the Idoc - wpuums01. Partner profiles are of type - Customer - and also there will be a seperate partner profile for each store.
But, Inbound POS data has store number and idoc doesn't have store number in segments E1WPU*. IDOC has sender partner number , which is store number in this case, in EDI_DC40 segment.
I think, we deactivate EDI_DC40 segment for inbound messages. If this is the case, how do we map store number in pos file with IDOC. If we keep EDI_DC40 segment active, do we have to map the fileds like tabnam, mestyp, idoctyp, sndpor, sndprt, sndprn, rcvpor, rcvprt, rcvprn etc...
thanks in advance for your inputs.

hi,
>>>>Can I select "apply control record values from payload" OR select "take receiver values from payload".
you can select take from payload and set sender
(two things) and the store number can be dynamic (from payload)
IDOC adapter config that you're looking for is described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Inbound Idoc Data mapping sheet

Similar Messages

Maybe you are looking for