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

Similar Messages

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

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

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

Errors while posting Delivery Idoc

Dear All,
We are changing some segments of an Delivery Idoc. After changing, the system is creating an new Idoc with the values defined in the original Idoc and is changing the status of original Idoc from 30 to 32. Then again we are changing the status of Idoc to 30 with the help of function module "IDOC_STATUS_WRITE_TO_DATABASE". Now, while submitting the original Idoc in WE14, a pop-up is coming with "1 Idoc Selected" but status is remaining 30 only. But since we have transferred this Idoc to the port so status should have changed to 03 which is not happening.
Please suggest me a solution for this.
Warm Regards,
N.Jain

hi
What i think is that you have to reprocess the idoc. Execute this program in se38.
RBDMANI2 : Reprocess Idocs manually
RBDMANIN : Posting of IDocs with Status 51
RBDMOIND : Outbound Idocs status 03->12
RSEOUT00 : For Processing 30 Status IDocs
RBDAPP01 : For Processing 64 Status IDocs
RBDAGAIN : Reprocess Incorrect Outbound IDocs
RBDAGAI2 : Reprocessing of IDocs after ALE Input Error
Reward points for useful ans.
Regards
Aarti
Message was edited by:
Aarti Dhingra

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 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

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
 EXPORTING
 pernr = ins_objects-objid "#EC DOM_EQUAL
 actio = 'INS'
 tclas = tclas
 dialog_mode = dial_mode
 luw_mode = '0'
 no_existence_check = $cross
 no_enqueue = $cross
 IMPORTING
 return1 = return
 hr_return = hr_return
 TABLES
 proposed_values = proposed_values.
 REFRESH proposed_values.
 IF hr_return-msgty = 'E'. "note 984409
 CLEAR protocol_error.
 protocol_error-msgty = hr_return-msgty.
 protocol_error-msgid = hr_return-msgid.
 protocol_error-msgno = hr_return-msgno.
 protocol_error-msgv1 = hr_return-msgv1.
 protocol_error-msgv2 = hr_return-msgv2.
 protocol_error-msgv3 = hr_return-msgv3.
 protocol_error-msgv4 = hr_return-msgv4.
 READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
 infty = hr_return-infty
 subty = hr_return-subty.
 protocol_error-segnum = t_hrobjinfty-segnum.
 protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
 protocol_error-msgty = hr_return-msgty.
 protocol_error-msgid = hr_return-msgid.
 protocol_error-msgno = hr_return-msgno.
 protocol_error-msgv1 = hr_return-msgv1.
 protocol_error-msgv2 = hr_return-msgv2.
 protocol_error-msgv3 = hr_return-msgv3.
 protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
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 Shipment IDOC

Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type in wWE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
Rishi

Hmm.. I don't think anything else is required for the inbound. Take a look at the control record of your IDoc - maybe it's not looking for the profile that you've set up in WE20. Partner # / type / message code must match.
Also make sure that in WE57/82 you have the standard IDoc type and your Z... extended IDoc type.

Error while testing Inbound Idoc

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
PL HELP!!!!!!!
The procedure followed by me was,
WE31 created custom segments,
WE30 Created custom basic type,
we81 Custom message type,
se37 function module,
we82,
we57,
bd51,
we42,
bd67,
we20,
Am not able to figure out why exactly is the error message being shown.
please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

Hi friend,
if it is help full please give max reward point.
Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
Two programs enable cross-system reporting:
     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report
IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
53 Application docu posted     =>     41 Application docu created in receiving sys
51 Error: Application docu      =>     39 IDoc in receiving sys. Status repeated
     not posted                         each time RBDSTATE runs.
68 Error: No further processing     =>     40 Application docu not created
ALE Auditing
BDM7          =>     ALE Audit: Statistical Analysis
BDM8          =>     ALE Audit: Sending the Confirmations
RBDSTATE     =>     Run on Receiving System to return Audit Message

Error in posting Inbound IDOC

Hi Gurus,
I am trying to create Vendor by inbound IDOC by enhancing the standard FM IDOC_INPUT_CREDITOR but IDOC is getting posted with status 51:
Status 51:
Trans. XK01 record 3 : Data record is not flagged as record type 2

Hi,
In Idoc if you have field STYPE pass in debug we19 STYPE = '2' and check if this works.
Raghav

Error while posting Inbound Delivery

I am trying to post inbound delivery and getting error that there is no item avaialble on the Purchase order. Please help.
Thanks in advance.

Hi,
Check Confirmation Control Key of resp. purchase order.
Also check for the said inbound delivery, have you created shipment for this?
If no, create with respect to Inbound delivery using transaction VT01N and then do GR agianst Inbound delivery.
Please check and revert.
Thanks
Hrishi
Edited by: Hrishi on May 30, 2011 10:53 AM

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 while testing Inbound INVOIC with we19

Hello Friends,
I want to test inbound invoic with we19.
I get now the mistake : external sender not avaiable (status 51) (translated from the german : Externer Sender wurde nicht angegeben).
I guess the INVOIC-Idoc ist correct.
Whal could it be?
thanks and best regards

Hi Check the following config
Data Transfer(System Settings for Idoc Interface
Define Conversion of External Item Identification
Basic Settings for Document Transfer
Also check the partner profile and check if you have additional segments for item data. If yes then maintain it Document transfer from external system
Hths
Saj

B1358 error while posting inbound idoc with a FM

Similar Messages

Maybe you are looking for