GL Balance Inbound Idoc Interface

Hi Experts,
We are evaluating the option of G/L Balances upload using Idoc (Interface) from Legacy System.
Basically I am looking for the Error handling Conditions in Idoc.
If anybody has experience on working on Idoc for GL balance upload from Legacy system, please share your experiences with me.
Appreciate your help on this.
Thanks
SJ

You can use IDOC type ACC_GL_POSTING01 for GL Postings and can use LSMW or any custom program for this IDOC.

Similar Messages

Inbound Idoc INVOIC01: Balance not zero

In ECC 6.0, we are using inbound idoc type INVOIC01 and function module
IDOC_INPUT_INVOIC_MRM to enter MM invoices & FI-postings for incoming purchase
invoices that processed in an external system.
The idoc raises error msg M8 534: "Balance does not equal zero".
While processing the idoc, tax amount is not getting posted.
I tried posting invoice through MIRO using the same data and it is getting posted but when i am using idoc , its giving error.
Has anybody run into a similar problem? Any hint would be extremely valuable in order to solve the problem!

Can anyone please help me on this ?

Vendor Credit Memo creation in SAP via IDOC Interface (Inbound)

Hello Team,
I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
Regards,
Vijay

Hello Team,
I have a client requirement to create Vendor Invoices & Credit memo via Idoc Interface. Iam using INVOIC02 idoc type for posting Invoices and could able to create the invoice successfully. For credit memo , I'm aware that we can use the same idoc type (INVOIC02) and need to pass CRME value for the segment field BSART.
What i need is a sample Inbound INVOIC02 idoc file for credit memo to identify the required fields for successful credit memo creation.
Regards,
Vijay

Updating transaction MD61 using information from inbound IDOC

Is there any standard IDOC type for Planned Independent Requirement(having fields of table PBED and PBIM in its segment)?If such an IDOC type doesnt exist then i have to go for custom idoc type creation
I have an inbound IDOC having 4 fields in its segment
1.SAP Material number
2.Plant
3.Plant Quantity
4.Requirement date
Now i have to use this information in IDOC to update transaction MD61(create a planned order).
constraints:
in MD61 screen1
SCREEN 1
Material radio button is defaulted to on. This must also be set in the interface. Material number will be valued from the input file.
Plant will be valued from the input file.
Version number defaults to 00, so that value should also be used for the interface.
Planning Horizon From and To dates will be the same date and valued from the input file.
Planning Period should be set to D for Day
SCREEN 2
Material number should default from SCREEN 1 input. The interface should also do this.
MRP Area will default from the Plant on SCREEN 1 input. The interface should also do this.
Version will default from the 00 on SCREEN1. If needed on interface, also default to 00.
Version Active checkbox will be checked by default.
Base Unit of Measure will default from material master.
Only a single date column will appear which should be the date input on SCREEN 1. Value this column with the quantity from the input file.
Input fields are highlighted in screenshots below.
After input is complete, use the SAVE icon to store the data.
Kindly tell me the approach to prepare this interface?

Done,used BAPI_REQUIREMENTS_CREATE TO DO SO

File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

Hi All,
Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
Anyidea what might have gone wrong??
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
+<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
<SAP:Retry>M</SAP:Retry>
Waiting for your answers.
Thank You.
Seema.

Hi Seema,
I think you are using mi_Orders05_In_Asyn as the IDOC interface.
Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
Let us know if that doesnt solve your problem.
Regards,
Sumit

Testing of an inbound idoc.

hi experts,
i have to create an inbound interface for processing message order/ordchg.I have a .txt data file .how do i test my inbound interface so that the data in the text file is passed onto the inbound idoc?
Valuable help will be rewarded.
Regards,
Shrita.

Hi shrita sharma
1)Generating Idoc as a flat File on the outbound.
2)Uploading File as IDoc in the Inbound System
1) Send an outbound IDOC data(ORDERS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
Good Luck and Reward me for the same ..!!
Thanks
Ashok

Idoc interface not found..

I'm attempting to pull in an XML file to Idoc and I'm getting an error stating "Unable to interpret IDoc interface ZINCOMINGINVOICE_CREATEFROMD01" in the monitor.
I have imported the Idoc into XI and mapped to it and the translation is working fine. I have also gone into IDX1 and IDX2 on the target R/3 system and on the XI system and setup the port and Idoc in the inbound list. I have also managed the port and setup the inbound document in WE20 and WE21 on the target R/3 system.
I have a couple questions.
1. Have I done all the setup?
2. With the Idoc of ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 and the setup above for WE20 inbound set to ZINCOMINGINVOICE_CREATEFROMDAT is that sufficient?
3. Likewise with the ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 idoc and IDX2 set to ZINCOMINGINVOICE_CREATEFROMD01 is that sufficient?
My inbound xml document is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <ZINCOMINGINVOICE_CREATEFROMD01>
- <IDOC BEGIN="1">
- <Z1BP_INCINV_CREATE_HEADER SEGMENT="1">
<INVOICE_IND>X</INVOICE_IND>
<DOC_TYPE>ZA</DOC_TYPE>
<DOC_DATE>2001-04-20T23:59:20-07:00</DOC_DATE>
<PSTNG_DATE>2005/05/02</PSTNG_DATE>
<REF_DOC_NO>123456</REF_DOC_NO>
<CURRENCY>USD</CURRENCY>
<GROSS_AMOUNT>4900</GROSS_AMOUNT>
<HEADER_TXT>[email protected]</HEADER_TXT>
</Z1BP_INCINV_CREATE_HEADER>
- <Z1BP_INCINV_CREATE_ITEM SEGMENT="1">
<INVOICE_DOC_ITEM>1</INVOICE_DOC_ITEM>
<PO_NUMBER />
<PO_ITEM>2</PO_ITEM>
<ITEM_AMOUNT>130</ITEM_AMOUNT>
<QUANTITY>30</QUANTITY>
<PO_UNIT>EA</PO_UNIT>
</Z1BP_INCINV_CREATE_ITEM>
</IDOC>
</ZINCOMINGINVOICE_CREATEFROMD01>

Hello,
I encountered the same problem. If you are sure to have configure correctly your IDX2 transaction, be sure you have import the idoc in the repository under the good composant.
For example if IDOC is for R/3 4.6, import your idoc under SAP APPL 4.6C or SAP BASIS 4.6C to use it in the directory with a component that you defined before in your SLD as a SAP R/3 product.
Regards,
Chris

File-IDOC, idoc interface error

Hi,
Scenario: File-IDOC (Multiple records in source file to be mapped to multiple CREMAS IDOCs) without BPM.
Modified the occurance(maxOccurs = 'unbounded') in XSD structure of IDOC(CREMAS) and saved it as external definition.
I have used this external definition in message mapping and interface mapping.
In configuration, i have used the same message interface (corresponding to external definition) as inbound interface.
Now, I get the following error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_Cremas04_multi_external</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_Cremas04_multi_external</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.

Hi,
>>I have used this external definition in message mapping and interface mapping.
In interface mapping you need to use Imported IDOC not External definition
This solves your problem.
let me know if you have any issues still.
Cheers,
Jag

How to trigger change documents based on inbound-idoc?

Hi experts,
Currently I'm working in on a project where I have to create an interface based on IDOCS. This is an interface for two SAP-HR systems.
If there are made changes in the dialog (gui) by a user, there will be created a change document, which can be displayed by report RPUAUD00. For the inbound-interface based on idocs it's important that there will also be created a change document in the system based on this idoc. We have tested this, but no change document is created.
Can anybody help me to solve this problem: "How to create a change document based on the inbound-idoc?"
Thanks in advance.
With kind regards,
Roy

Thanks for responding. First, I like the idea of defining an event, but I'm still stuck with how to trigger it. I looked at dynamically registering events, and maybe doing something where a click on the graph control registers an event for key presses on the vi. I'd still have to figure out out to terminate the key press event. Unfortunately, (actually it's a feature I like..) there are a number of different ways to complete typing in a scale change. I routinely use ctr-enter (habit from working on a laptop), though enter works fine, and clicking somewhere else is probably the most common method. I am not that familar with User Defined Events, so I may be overlooking something obvious here.
The graphs are a Bode Plot, with a seperate graph for RPM vs Phase Lag, and RPM vs Magnitude. I want them to always be plotted on the same x-axis. The plot is generated when the user doubleclicks on a dataset. After that, it's just the user looking at it. They can change the axis without any new data being generated.
Thanks,
Chris

Message variant is missing in INBOUND IDOC.

hi,
Any one can help on this issue?
The sender has confirmed that message variant was filled in outgoing file.
However, When we received this Inbound IDOC, the message variant is blank.
I still am confused by two questions:
1. The function module which insert record into table EDIDC and EDIDD, is same as the function module which post this IDOC to sap module(normally we maintained it in WE57)
2. We normally need to maintained in WE57, but also need create one processing code, what is relationship between WE57 and processing code(WE42)

Hi,
Message Type/Message Variant needs to be maintained in WE20 ( Partner Profiles). In case of inbound IDOC ( receiving the data other systems) Data processing/posting will happens via function module. the function module will attach to the process code.
Process Code : The IDoc interface uses the process code to find the business process which controls the conversion of the IDoc into the SAP document.
The Process code will assign to the function module in WE42, the same function module will assign to the Message type and Idoc type in WE57
In a short summary, The Function module required to post the Idoc/update the data in SAP. However the Function module should process specific to the Message type and Idoc type only. It means the settings is required to identrify the correct function module to process the Inbound Idocs.
Whenever there is a problem with ALE setting the message 64 will trigger, it means the IDOC is ready to transfer to the application ( process through FM ).
Thanks,
Kiran.

Inbound IDOC status is strucked at 64

Hi,
My rerequirement is as follws.
Inbound IDOC process:
Through inbound IDOC i have to create the new sales orders and need to change some information to existing sales orders means 2 cases.
1) Create new sales order
2) Change existing order.
Iu2019ve generated two example IDOCs from order interface
one for an u2018order addu2019 and one for an u2018order changeu2019.
The times each IDOC reached each status are shown below:
IDOC 1677672 u2013 Order ADD
Status: 50 Started         Time:    09:54
            64 IDOC ready               09:54
            62 Direct Call                 10:39
            53 Order Created           10:39
IDOC 1677684 u2013 Order CHANGE
Status: 50 Started         Time:    12:50
            64 IDOC ready               12:50
            62 Direct Call                 12:50
            53 Changes on Y-table   12:50
Can anybody explain why the first IDOC had to wait for the scheduled
u2018IDOC PROCESSINGu2019 job to run, before it moved from status 64 to 62. But
the second IDOC appears to have been processed automatically without
waiting for the next run of the scheduled job?
Obviously, the u2018automaticu2019 processing of the change IDOC is the way we
would prefer it to work all the time).
Can any body explain in first case why it's taking time and in second case it's processed immidiately.
Regards,
Janardhan

Hi,
I believe you are using two different message types for this purpose. One to create order and one to change order. Did you check the partner profiles for these? May be partner profile(WE20) for creating order is set as "Collect Idocs" whereas the partner profile for the message type to change order is se as "Trigger immediately".
Hope it helps.
Regds,
Rudra

Inbound IDoc: Field BVTYP is missing

Hi,
I am new to IDoc I need help with a scenario. We have an interface wherein AP documents are transported to SAP. When we are viewing these IDocs in SAP field BVTYP (Partner Bank Type) is missing
Thanks in advance

Hi,
Are you dealing with inbound or outbound IDoc for sales order?
I am a bit confused ... you mentioned the IDoc successfully posted (inbound IDoc?) however outsource EDI team reported that field ZEILE is missing (outbound IDoc?)
Regards,
Ferry Lianto

** Inbound IDoc - One field is missing but it is displayed in SXI_MONITOR

Hi Friends,
We have developed IDoc to IDoc scenario. Source IDoc is sent from 3rd party system. Target is an Z IDoc (Replica of VEHCLE01 IDoc).
When we test the source IDoc XML from RWB, the message processed successfully in SXI_MONITOR and target IDoc is also created in backend SAP system. But, the problem is that, in target payload there are 5 fields. But, in the physical idoc created in SAP system has only 4 fields. The last field is missing.
Since it is inbound IDoc, I deleted the IDoc meta data in IDX2 txn, and reimported again the Z IDoc. But, again the same problem is coming. i.e one field is missing in inbound IDoc. But, in the receiver payload, that field is there with value.
Kindly clarify, friends.
Kind Regards,
Jegathees P.

HI,
If that field is missing for first time in R3 means(ie Receiver system, Idoc posting in we02) , then
XI side:
1. u have check whether that field is existing in Target Interface,Target Message in Interface Mapping
2. Make sure that u have mapped that field in Message Mapping.
R3 (receiver side)
1. Plz check we30 , whether that field is there for that ZIdoc structure
2. Take the same Idoc which got posted , test in we19 whether that Idoc getting posted with that field or not?
check whether ur Idoc structure is activated in XI
Thanks
Praba

Error status 51 no revere entry provided for Inbound IDOC FIDCCP01

hi experts ,
I am receiving an INCOUND IDOC from Sap XI Server .I have given the segements below but my question is if the @nd line item is given while receiving how do i post as i am getting Error 51 .
Please explain if i need to create more than one line item how do i post the idoc .do i need to copy E1F1seg and create it using code (program).
for the current existing file does not have a reconcialliatry entry given in the idoc file .Please let me know on how to post this idoc using bapi or what is the way .E.g
E1FIKPF : FI Document Header (BKPF)
BUKRS : Name of global company code
GJAHR : Fiscal Year
BLART : Document Type - SA
BLDAT : Document Date in Document
BUDAT : Posting Date in the Document
MONAT : Fiscal Period - 05
TCODE : Transaction Code - FB01
WAERS : Currency Key
HWAER : Local Currency
GLVOR : Business Transaction - RFBU
E1FISEG : FI Document Item (BSEG) -1
BUZEI : Number of Line Item Within Accounting Document
BSCHL : Posting Key - 40
DMBTR : Amount in Local Currency
KOSTL : Cost Center
HKONT : General Ledger Account
WERKS : Site
E1FISEG : FI Document Item (BSEG) -2
BUZEI : Number of Line Item Within Accounting Document
BSCHL : Posting Key - 50
DMBTR : Amount in Local Currency
HKONT : General Ledger Account
WERKS : Site
in th above given example the line number one is provided by the xi system but the line item two with posting key 50 is not given in idoc file

You either have to get the offsetting CR for your entry in the IDOC.....or get your FI/CO people to tell you how to construct, particularly that GL Account No., and replace any standard SAP process code and function module with a custom one that will put the JE back into balance. First solution is more preferable obviously. I guess I would question why this inbound IDOC process has been set up to present incomplete data for posting to FI/CO.

Inbound Idoc to create SD invoice thru VF01

Hello All,
I was looking for an Idoc that allow me to create an SD invoice (and automatically then an FI posting) based on an SD order (as VF01).
I found some consultants talking about INVOIC, others about ACC_BILLING.
But after somes tests, none of the above works as expected. (-may be I am using a worng process code...)
Is there an Inbound Idoc where I can mention the same data as I will do in VF01 to generate an SD Invoice ?
Thank you All

There is no inbound IDoc, to my knowledge, and it'd be a very unusual scenario that would require invoicing through an IDoc interface. As soon as all the preceding transactions have been completed, not sure what sense it would make to wait for some kind of interface to give OK for the invoice creation...
Anyways, there is an option to run billing through a background job, which could be scheduled at regular intervals or based on an event. It'd be a very short program to get a document # and to trigger an event for the job or just run SDBILLDL directly, whichever is preferable.

GL Balance Inbound Idoc Interface

Similar Messages

Maybe you are looking for