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
Similar Messages
-
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
krishnaHi 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 -
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 AMHi,
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 while trying to post inbound idoc of message type COND_A
Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
MohitI do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated. -
Help required in posting inbound idocs
Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena GeorgeHi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George -
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
-
How to post inbound idoc in sap system?
Dear All,
How to post inbound Idoc in sap system?
Regards,
Amar
Edited by: amar kumar on Nov 23, 2009 2:53 PMHi Amar,
Use the FM IDOC_WRITE_AND_START_INBOUND to post an inbound IDoc. Just build the EDIDD and *EDIDC8 tables and enter a profile for a inbound message type from a partner. It returns a IDoc number. Don't forget to do commit work.
Regards
Abhii -
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 replyHi,
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 '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 -
Urgent help required : Batch processing error of an inbound idoc
hi,
i have a problem while posting an idoc to the GL(FB01).
i'm using an Inbound idoc message type : ACC_GL_POSTING
idoc type : ACC_GL_POSTING01.
Process code : BAPI.
In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
i have set the option " Trigger by background program" in the partner profile (we20).
while testing the process i'm getting the error "Document type -- is only defined for batch input".
how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
with regards.
T.Jeyagopi.Jeyagopi,
There are different types of Data loading into SAP.
BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
In my opinion it should work.
Regards,
Ravi
Note : Please reward points for the posts that help you. -
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 -
Handling of Error(s) for Inbound IDOCs
Hi Gurus,
I have an requirement where we need to handle and correct the error if inbound IDOC fails. This inbound will be for Account Document posting.
Please let me know how to handle this issue.
Thanks in advance.
Regards,
Gajanan<b>Hi,
smells like workflow task.
DI Information
Message type
INVOIC
IDOC type
INVOIC01, INVOIC02
X12 transaction set
810
Edifact message type
INVOIC
Workflow in case of error
TS 0000 8056</b>
Executable program
IDOC_INPUT_INVOIC_FI
Regards,
Clemens -
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.
-UmeshHi,
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 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?
RishiHmm.. 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.
Maybe you are looking for
-
Need help to get alternate or better way to write query
Hi, I am on Oracle 11.2 DDL and sample data create table tab1 -- 1 millions rows at any given time id number not null, ref_cd varchar2(64) not null, key varchar2(44) not null, ctrl_flg varchar2(1), ins_date date create table tab2 -
-
I'm trying to get a basic TV to work as a remote monitor on my HP Pavillion laptop. The picture is fine - but there is no sound. It's connected via the RS232 AV output socket and the OS is Windows 7 64bit. Be very grateful for any ideas?
-
How to reset safari 8.0
The reset option is missing in safari 8.0. How do I reset safari 8.0?
-
Check disk space thru database
Friends, Is there a way to run the command say "df -g" through the database and get the output so that to display it finally in the database?
-
hi Here to t-code is LX47 which is ment for the delayed delivery date and the problem is when i run the t-code i given the warehouse no and activate the activate item analyze TO item here also i activated but the result is not showing the error i