Error in posting the Idoc....

Hi Experts,
When I post the Idoc from the external system to the SAP,I am getting the
error as application document not posted and status code as 52.so what I need
to do to overcome this error,please help me over this issue.
Regards,
Kiran.

Hi,
you have to check the idoc in debugg mode and pull it out the reason why i has 52 and you know how to debug inbound - go to we19 and here give any existing idoc no and press F8 and enter into screen, in that select 'INBOUND FUNCTION MODULE' select give ur standard F.M name and select the background mode.
or thre way is goto BD87 make the correct the error idoc manually.
--Use Tcode BD87 to check for IDocs that are not been processed and reactivate.
u can find here if any data wrong or missing.
<b>Reward if useful</b>
Regards,
Vijay

Similar Messages

Error while posting the IDoc for Customer Invoice.

hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
Even in f-22 also it is not asking for the same.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Error while posting the IDOC. Status message '56'

Hi,
I have a requirement where I will post an IDOC which inturn will split the original IDOC into child IDOCs based on the store value.
I am trying to post the IDOC in WE19. So, the Original IDOC is posted successfully with status '53'. Whereas, the child IDOCS finished with error. The status of the message is '56' and the error says 'EDI: Partner profile not available'. Could someone tell me what could be the reason for this..?
Actually, the IDOC was created by the Functional Consultant. So, should the partner profile creation also done by them or do we need to do anything to solve this problem.? Could someone answer me this question. Thanks in advance.
Best Regards,
Paddu.

It looks like the control data for the child segment is not getting populated. you have to find the code which populated the control data and see if it is doing what it should.

Error while posting the Idoc 'Update error, transaction VA01'

Hi Gurus,
When an inbound Idoc for sales order is trying to post we are getting the error 'Update error, transaction VA01'.
Aslo following are the details of the error:
Update error, transaction VA01
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
Update information
Return code: 009
Text : Error during insert table FPLTC (RC= 1, Key= )
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.
Can somebody let me know what would be the cause.
Also the we are trying to post the Idoc with a Id which is having maximum Authorization.

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Error when posting the IDoc

Hi,
Now i am working on a File (XI) to IDoc (R/3) scenario. In XI, I went to the TCODE "idx5", there is no error. But When I went to the TCODE "idx5" in R/3 side, it showed me the follwing error...
"No authorization to send IDocs with message type ZEMPINFMSG".
What role should i assign to the user?

Hi Jeya,
Have you tried to post IDocs from the R/3system?...goto we19 and try to send an IDoc. In XI, to check if the IDoc has reached-t-code is IDX1..
Regards,
Sushumna

Error while posting the CREMAS03 Idoc

Hi
I a getting the Error while posting CREMAS03 idoc from File
The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
but when i cheked with the functional guys , the comany code exits..
Any one have any idea
SV

Hey,
    seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
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)
     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 6)
     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.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
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.

Error oocuring after posting the IDOC

Hi
i am getting a error in a scenario
the scenario is Idoc to file. when we post the IDoc, its getting posted successfully. but the pipiline is getting failed at the inbound message when monitoring in SXMB_MONI.
i am getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIAdapter</SAP:Category><SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/>
<SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server
</SAP:Stack><SAP:Retry>N</SAP:Retry></SAP:Error>
all the experts help me out in solving this issue

Hi Deepika,
their might be some problems with ur ALE settings.
Here is a detail of the steps to be followed.
Do verify whether u have done the steps or repeat the steps as stated:
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)
     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 6)
     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.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
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)

Error while posting Inbound Idocs-"EDI: Partner profile not available"

Hi,
I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
I have done the following steps so far
1.Created IDOC basic Type and Message Type. (Custom)
2. Created process code to process the IDOC.
3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
4. Use the FM IDOC_START_INBOUND to process the IDOC.
Is ther anything else that i have to do inorder to post the idoc sucessfully.
Thanks in advance
-Nishant
Edited by: nishant patel on Nov 13, 2009 10:35 AM
Edited by: nishant patel on Nov 13, 2009 10:41 AM

Hi,
Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
Hope this helps
Regards
Shiva

Error when posting the goods receipt

Hi we have recently successfuly updated 4.6 B to ECC 6.0.But when i am doing captive consumption by 949 Mvt. through process message system gives an error that
Error when posting the goods receipt
Message no. CB345
Diagnosis
With the selected process message, a goods receipt for the order was reported to the warehouse (destination ZPI1). However, an error occurred when the goods receipt was posted.
Please do needful.
Regards,
PP

Hi Daniel,
This is the first time i am coming across an issue like this.
neverthless from a logical front,
1. Remove Cost center as a valid receiver in Settlement Profile.
2. Your OKB9 setting are pretty much good. No need to worry about it. Becasue, OKB9 only will work if the system doesn't identify any other cost object. In this case Production Order is an automatic cost object which system should have taken.
3. Check the Settlement rule when you have created Production Order. It should have been MAT.
4. I hope you are creating Production Order with Material (using CO01 and not CO07)
5. Make sure in OPL8, the default rule in controlling tab is PP1.
Once all these are fine, i do not see any reason why you will get your probelm.
Please check and revert back to me if the problem still persists.
Best Regards
Surya

Sample coding for creating a function moudle to post the Idoc

hi,
I am working on Inbound idoc,
Aim : to update the Ztable
I have created the message type , idoc type and the segment type.
For creating an idoc i have used the Function module IDOC_INBOUND_WRITE_TO_DB.
Now for posting the idoc, i need to create the function module, the main aim is to insert record to the Ztable, what should be my input and the output parameters,
Can u provide the sample coding for it

As you are dealing with a IDOC, the parameters will have to be standard as any other IDOC processing function module. For example take a look at IDOC_INPUT_BANK_CREATE.
You will have to read the data exactly the way the standard code does and the only change will be once you read the data how do you want to handle the data.
Regards,
Ravi
Note : Please mark all the helpful answers

How to find the user exits called at the time of posting the IDOC?

Hi,
Could anyone please how to find the user exits while posting a idoc?

Hi,
One way to ahive this is by, be ready with IDOC postiong,
then go to ST05 transaction and activate the trace after checking Table Buffer Trace.
Now post the IDOC then deactivate the trace.
Now come back to ST05 and display trace and search for calls starts with EXIT_.
Regards,
Manoj Kumar P

Error while posting Invoice IDOC (The difference is too large for clearing)

Hi All,
While posting Invoice IDOC to Remittance Advice IDOC get fails with status 51 & message ' The difference is too large for clearing'.
Please suggest any solution or reason to fail IDOC.
Thanks & Regards,
Ajay
Moderator message: please search for information and try to find out yourself before asking, this will be a functional problem anyway that should be asked in the appropriate forum, e.g. ERP Financials.
locked by: Thomas Zloch on Aug 20, 2010 1:59 PM

Pls check the tolerance amounts limits:
SPRO--- F/A --AR/AP -
Business transactions -Open item clearing--- Clearing differance---- Define / Assign tolerance groups for emp -
Where you need to change the limits of max amounts with the %
Let me know for any info.
Regards
Suresh

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Variables passed to Function module for posting the Idoc

Hi,
For Posting the Inbound Idoc a Function module is created what should be the values passed to
1) return_variable and
2) workflow_result.
I saw in many of the program like this if there is an error in posting.
I gave return_variable-wf_param = ' Error Idoc'.
and workflow_result = '99999'.
Why are these values passed, where are they used.

Josephine,
In your parntner profile for your customer/vendor ( depending on your idoc type and business scenario) , you would have assigned the post processing permitted agent.
In case the function module errors out, these values are carried out to the WF container and appropriate post processing notifications are sent to the agents. That is the purpose of having these variables in here.
It could be a success/failure, agents are notified in either case.
Ganesh

Object (MARA) not found error while posting CLFMAS Idocs

Good day,
We are migrating the class hierarchy using Transaction CLHI (mesg. type - CLFMAS) from one SAP system to another.
When we try to post CLFMAS Idocs in the receiving system, we are encountering this error-
Object < > from table MARA has not yet been created. For this reason, no class allocations can be maintained for this object.
On further research, we found that this class (say parent class), has a subordinate class assigned to it that gets sent in the Idoc. The child class is not present in the receiving side, hence the error.
Now when we try to ALE the child class first (before the parent), the same idoc as above scenario gets created with the same error that the child class is not present.
These are our field values in the Idoc-
Segment E1OCLFM MSGFN   004
                                 OBTAB MARA
                                 OBJEK   Child (or subordinate class) class
                                 KLART   001
                                 MAFID    K
                                 Object_table MARA
Segment E1KSSKM MSGFN   004
                                 CLASS   Parent class
                                 DATUV   00000000
                                 STATU    1
There is one other issue that we are missing is that we are trying to migrate the material
classes/ hierarchies. We are not yet mapping the material # to it. Why is it that the object table name is MARA.
Please advise. TIA!!
Liz

Hi!
Any ideas anyone?
TIA, Liz

Error in posting the Idoc....

Similar Messages

Maybe you are looking for