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.

Similar Messages

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

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.

Mapping of large INVOIC Idocs

Dear SAP,
we have a 1:n mapping scenario.
The source is an INVOIC Idoc that will be splitted into several messages.
The INVOIC IDoc has a sice of 5MB and more than 35.000 data sets.
Because of the huge number of data sets / positions, there are two new
child-segments containing the data sets (see attachment).
INVOIC IDocs with only eg. 100 data sets has noch such child-segments
(see attachments).
In PI message mapping there is an error while mapping large INVOIC IDocs:
While 1:1 mapping of positions (E1EDP01) the text segments
(E1EDPT1/E1EDPT2) are not mapped correctly.
While mapping a position of child-segment ONE the text is mapped from a
position from child-segment TWO.
In our case the 166th position of child-segment ONE is mapped, but the
text is comming from the 166th. position of child-segment TWO.
The text mapping is 1:1. It works without errors while proceeding smaller INVOIC IDocs.
We can´t explain this behaviour.
Also the standard INVOIC structure does not provide such child-segments
while uploading into PI.
Is it a buffer problem in PI?
Is there a maximum number of data records in INVOICE IDocs?
Do we have to adjust the INVOICE structure in PI?
Thanks in advance,
André

Is it a buffer problem in PI?
Could be, but I have used bigger message size without any issues. If your mapping is not too complex, could you write an XSL mapping and check if you run into similar situation? Message mapping has definitely cache issues, hence I prefer XSL.
Is there a maximum number of data records in INVOICE IDocs?
No.
Do we have to adjust the INVOICE structure in PI?
No need to adjust the structure, just try with XSL mapping.

Invoice List data(VF21/VF22) as IDoc

Hi,
We have a typical scenario of converting Invoice List data in SAP into IDoc and to transmit it as an XML to the third party system. In the data to be transmitted, sub-totalling at the material (in the invoice items) and material+invoice date level is required and the sub-totals are to be populated in two kind of segments (for each of the sub-total type) in the IDoc.
That is, a new IDoc structure will be defined with the segments/fields that the customer wants viz., a header segment with only few fields from the invoice list header, an item segment with only few fields from the invoice list item, and a sub-total segment with two fields, each to hold sub-total at material and material+date level respectively.
We have output types which, when assigned in the invoice list should create the required Idocs.
Invoice lists will be created for several partners, but each list will have only one partner.
What are the steps to be carried out in order to achieve this objective? Please stress upon the FM parameters to be provided and NACE options to be selected.
Vish.

Hello ,
Your requirement is very simple ,However before posting into sdn please do a proper search on idoc.
Now coming to your requirement as of now you have the invoice data coming up.
1. In the NACE transaction create an output type related with the respective partner data.
2.Create segments with the required fields and set its status to release.
3.create Idoc type and message type ..link the message and segents.
4.Now link the message type and idoc type .
5.
6. Now assign process code to the partner function by defining a logical system and in the process code
put your custom function module where you put your custom code which will filter and
cumulate the data coming from the invoice into different fields
using normal abap code,
Now once you are done with the abap coding the
function module has few parameters which you can pass them as it is .
control_in need to be passed to Control_out as it is.
Now fill the segments with the required data and append the segment data to the
EDI_DATA structure which is a exporting parameter for thefunction module .
Now once you execute the invoice using this partner function and message type
system would internally call the custom function module which you have assigned to
the process code and would create an idoc.
also go through saptechnical-com site for addition details on idoc creation.

Legacy data(mapping to be done by xi (in xml format)) to sap using idoc .

hi all,
I need to work in an object in which requirement is like , the source data is directly extracted from legacy and input file is made. now i need to create an interface program which will be used to create purchase req. in weekly basis. now according to functional specification xi team will map the source data in xml format and then through idoc data is to be pushed into sap. i am confused about the step by step senario from source data to final pr creation . please clarify if somebody had worked on this kind of situation.

Hi i encounter like this but in SD side,
from legacy ->XI -> SAP (create SO)
then from created SO via IDOC my requirement is to post delivery then billing.
I think in your case the PR is already created and to be process to PO.. better check and fully understand the flow with your team.

Inbound Invoice IDOC mapping Required fields

Hi All,
Please let me know what need to be mapped for the @begin , @segment , TABNAM , SNDPOR, SNDPRT etc like this elements in the IDOC structure.
In my scenarion i get Invoices in XML file so that i can pick that and process it into SAP R/3 by doing correct mapping with the inbound IDOC and post the same into R/3 . Please provide the sample mapping for processing Invoice IDOC.
Regards,
Reddy

Nanda,
@ Control records
>>>
You have two option. One is to fill the control records inside the mapping or else let XI fill it automatically.
In case you are filling the control records in the mapping, then you will have to enable the option to take those values in the IDOC receiver adapter.
See option (Apply Control Record Values from Payload) - http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm
Control values - http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
@ Begin, Segment etc
>>
you can map any constant value to the same.

Inbound Invoice idoc segment feilds mapping to SAP feilds

Hi,
Could you please help me to find out the tables and feilds in SAP for the inbound invoice idoc type INVOIC01. I need to map the idoc segment fields with SAP fields and respective tables.
Thanks in Advance
Satish

Hi Satish,
That's quite a big case to get such mapping - why would you need it really? You can process Idoc with std process codes and you will see the std mapping then happening.
You can also go through logic of processing modules:
Function Module Name          Short text for function module
IDOC_INPUT_INVOIC_FI           EDI: Invoice Receipt (INVOICE)
IDOC_INPUT_INVOIC_MM           EDI: Invoice Receipt (INVOICE)
IDOC_INPUT_INVOIC_MRM
For sure you will get RBKP for header, RSEG for items, RBTX for taxes and some more, depending on what you get in the invoice and what are your booking and matching processes.
Best Regards,
Tomek

Employee Data Mapping - Partner Idoc

<b>Hallo all,
I need to map the employee data of the legacy system to an Idoc(For migrating data with XI). I functionally mapped the fields in the legacy system to the fields in CRM BP master data(Most of them). I have selected the BP complex Idoc(CRM_XIF_PARTNER_SAVE) and mapped most of the fields(name, address, Phone Numbers, Position etc ).
the following fields are yet to be mapped
Employee No
User Name
Contact Role
Executive role
Corporate tile
Affiliate subsidary
Is there any other standard Idoc to map the employee details (or) am I supposed to enhance the complex Idoc.
Please let me know ur suggestions
regards,
MAX</b>

Hi Max,
yes you are using the right Idoc for creating business partners (employees) as this follows the middleware data distribution. There is a badi available for this as well for if needed CRMXIF_PARTNER*.
Cheers
Andrew

IDOC Segment mapping change

Hi,
How can i change the field attached to a IDOC segment.
Actually we have this Invoice IDOC,in which the E1EDK03 012(Qualifier) is passing the IDOC creation date instead of Billing date.
So i need to change this mapping to Billing date.
Please help.

Hi Salz,
I just checked my version of SAP (4.7) and you should get an invoice date. Check out the subroutine FILL_E1EDK03 in function module IDOC_OUTPUT_INVOIC. The first section of this code creates an E1EDK03 segment with the invoice date (if there is an invoice date), with qualifyer 026.
Is there a possibility that in fact you are getting an E1EDK03 segment with the invoice date, but you are also getting other E1EDK03 segments (such as the one you mention with qualifyer 012) and they are obscuring the one you are looking for?
If there are definitely none being created then can I suggest that you debug the subroutine FILL_E1EDK03 in function module IDOC_OUTPUT_INVOIC to check what is happening. You may need to change the timing of your output record to 1 and run the program RSNAST00 online to get the breakpoint to be hit correctly.
If, in your version, the code doesn't include this date, then you have an exit function module EXIT_SAPLVEDF_002 (called via the subroutine CUSTOMER_FUNCTION in function module IDOC_OUTPUT_INVOIC) where you can actually add your own segment data. For example you an change the contents of an existing segment (as per your original request), or append your own E1EDK03 segment with your own data. I would recommend adding your own segment rather than changing whats there.
It is possible to extend idocs to add your own custom segments (eg Z1EDK03), but I wouldn't recommend it in your case, because in later versions of SAP the date is provided and by not creating a new segment (Z1EDK03) you will have no mapping changes to do when you upgrade. You can just delete your userexit code.
Hope that all makes sense and helps you with your problem.
Cheers,
Brad

Idoc data in flat file structure

Dear Experts,
We have idoc data in flat file structure. We need to fetch it using ftp and map it to an idoc.
please tell me how to proceed .
Thanks,
Aju

Hi,
For flat file you need to use the File content conversion parameters.
Refer the blog,
SAP Network Blog: How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
How to process flat files with multiple documents like POs, SOs etc. in a File to IDoc scenario
Thanks
Swarup

Error in Invoic Idoc - Vendor, Company code not found

Hi All,
We are facing an issue with an Incoming Invoice Idoc (Mes type - Invoic). A third party system sends the Invoices which are received by the XI system and then as Idocs into SAP.
The XI system is defined as a Logical system in R/3. We have created Partner Profile, Dist Model with XI as a LS.
The error that we are encountering is -
Customer , vendor <our LS> not known
Message no. FD110
A company code cannot be determined for LS
Message no. FD006
Are we missing out some data in the Idoc or are we missing some EDI configuration?
Please advise as to how we need to proceed.
Thanks in advance!
Liz

hi,
Error : A company code cannot be determined for LS
This means that SAP cannot match an appropriate company code with a partner profile :- and hence, doesn't know where to post the invoice.
Partner Type = "LS" (Logical System)
Partner Name = ""
I think what you've got is message FD006 - longtext for it can be found via transaction SE91 and sounds like this:
The system cannot determine the relevant company code since the allocation of the data transferred in the invoice is missing in Financial Accounting customizing.
The company code can be determined outside of the system and be put into the intermediate document (for example, from the EDI subsystem). Then the company code must be put into the E1EDK14 segment and ORGID field and the value "011" used as the qualifier.
Determine the company code for & & & in Financial Accounting customizing.
LS is your Logical System. So you might want to have a look at transaction OBCA where you can assign a company code name in the invoice for your Logical System.
In the E1EDKA1 segment. there are two fields PARVW (which is the qualifer or Partner function) PARTN (partner number). The information that is sent in the PARTN has to either match the information in SAP or has to be converted.
If the later is the case try transaction VOED.

XML IDOC data (hosted on a web server) & handling multiple WSDLs

Hi ALL,
1)how to design an Interface for picking up an XML IDOC data (hosted on a web server) which will be uploaded to SAP or converted to a file
this is what the customer has given me ..can any one explain me this and help me how to more forward
2).This Interface must use UDDI concept because we are going to use multiple BAPIs /RFCs as WSDLs
what is this mean can any send me some document on this
3).Use web-service navigator concept as we will be handling multiple WSDLs
i worked on 1. to define a place holder in WebAS for holding the
wsdls.
2. publish the wsdls in WebAS UDDI Repostory
but i have never used web-service navigator concept as we will be handling multiple WSDLs what is the difference ..send me some step by step docs ..
thanks very much
RK..

1.I am not clear with the requirement too. THere is no big deal in sending XML to IDOC or File. Based on your requirement you have to import IDOC structure or ify ou are using file, create a structure for the file.
If u are asking about sendin the XML directly without mapping, even you can do that without MM and even IM.
Please be more elaborate and if you are not clear with what client said, paraphrase them or ask again. Its not good to start work unless we are very clear with the requirement.
you can say to my understanding i feel this, now pI will send data like this. Is it correct?
2. More information on UDDI
http://en.wikipedia.org/wiki/UDDI
I dont think you need to worry much about this now with many features provided in ESR especially
3. http://<Host>:<port>/wsnavigator/
The webservices going out of PI are published here.
provide host and port are host and port details of ext system.
Once you enter link in your browser, it shows the available webservices hosted there.
All you need is to click on the required wsdl and test it.
It is as good as sending your data from PI to other system.
It is similar to Altova XML spy but the difference here is you enter the values directly here but in XML spy we send XML .

XML to IDOC : Hierarchy mapping help needed

Hi All,
I am trying to complete graphical mapping for an XML to IDOC structure. Both structures are EXACTLY same, but data is not populating in IDOC as desired.
My incoming XML structure and IDOC structure is
Header
Data_header (1 -- 999)
|_Data_item (1 -- 3)
Trailer
If I have only 1 header, then IDOC data is populated correctly.
But when I have multiple headers and theer items, the Headers are getting populated, but items do not get populated correctly.
*Example My Input is:*
Header
Data_header
|_Item_1
|_item_2
Data_header
|_item_3
Trailer
My output is (IDOC)
Header
Data_header
|_Item_1
Data_header
|_Item_2
Trailer
As seen above Item3 of Data_header2 has gone missing._
For Data Header, I am using REMOVE_CONTEXT function and for ITEM I am using SPLITBYVALUE. Thought this should have helped, but am struggling.
Any tips, help, greatly appreciated.
Many thanks
Shirin

Hello,
Have you done one to one mapping, as u mentiong they are exactly same..
if that's the case, then mapping test should be successful.
If there is any diffrence in occurences of target structure or any other difference and let me know.
If possible send me the target structure...
Regards,
Sreenivas.

Invoice IDOC data mapping

Similar Messages

Maybe you are looking for