Inbound Idoc in XI system giving error 56.

HI Experts,
using we19, i have successfully sent data from my r3 system. In the receiver XI system, it is showing error 56 in we02. Pls help.Where have I missed out data.
Secondly, in case of sending an Idoc with data using we19, we can confirm data has passed out successfuly from sender system, is there any way I can confirm data has passed/ failed to pass from an RFC to the receiver system, within the Sender system??
Arnab.

hi Mondal,
First of all, If the Idoc has generated at R/3 side and u didnt receive at Xi means
1) Check in IDX5 at XI
2) Check in SM58 at R/3
3) Check in SMQ2 at XI
Thats it , these will give u some clues
generally error is indicated in sending system with numbers 51 and 56.
51 Application document not posted
56 IDoc with errors added
Refer
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm
Thanks
Sushma

Similar Messages

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 PM

Hi 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

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Using Inbound IDOC from Java system creation of Outbound delivery

Dear Experts,
The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Thanks for the feedback. This question is resolved

75% of overhead to be loaded on WIP. System giving error: Msg No. KJ333

Hello Experts,
We are executing WIP (TCode: KKAX). We have load only 75% of the overhead. Hence for this, we have maintained 3 things ReqToCap - OVH,
OptToCap - OVH and % OvhToCap as 75%.
However, system is giving error. Refer Screenshot KKAX Error - 1. Refer my setting Screenshot - KKAX Config1
Since it was multiple assignment error, I tried removing "ReqToCap" It gave me other error. Refer Screenshot KKAX Config2
Please help me, how to achieve this requirement.
Deepak

Dear Deepak
Your OKGB screen should look like this:
Kindly update, after changes did it wok or not.
Regards
Rajneesh Saxena

While doing MIGO system giving error massage "No account was specified for account type "D" in item "0000000001"

Hello,
While doing MIGO system showing error " No account was specified for account type "D" in item "0000000001"
Kindly help me to resolve this issue.
Regards,
Abhijit

Hi,
Your issue seems to be an issue in FI. Refer the similar thread: MIGO error for UNBW material and the note: 1027645 - Message F5670: Account not specified in item X
Found a similar issue in J1IS as explained in the KBA: 1932095 - Error : F5670 - ' No account is specified in item 0000000002 ' - in transaction J1IS
Regards,
AKPT

How to send back the stauts of inbound idoc to outbound system

Hi all.
Idocs are scheduled to send from outbound to inboud.In inbound I have many idocs with status 51.(application document not posted).I need to report back the details of all the idocs with status 51.(application document not posted) .ie I need to send the idoc no, error message,error data from inbound to outbound on daily basis. Can any one let me know how to achieve this.i.e How to trap the details of idoc with status 51 in inbound & send this details back to inbound.
Can it be done by audit reporting of idocs? Or do I need to write a program?If so pls guide me.
Thanks in advance.
kind regards,
Samiulla.

You will have to setup the acknowledgements in this case. Message type ALEAUD.
This will be setup in the WE20 of the receiving system to be sent to the sending system.
regards,
Advait

Inbound IDoc incurs FI/CO interface error: Line item entered several times

We encountered an error in an attempt to post a financial transaction document with multiple line items. The Paid In/Paid Out IDoc 210266 was created in the transaction WPUF as follows:
Customer: 711
Transaction Date: 08/22/2008
Transaction Type: ZPOU (Paid out)
Item __ Acc.assgnt obj. ____ Cost Ctr __ Amount __ Crcy
1________________________7110150____100______USD
2________________________7110150____100______USD
1________________________7110150____200______USD
2________________________7110150____200______USD
The IDoc status was 64 (ready to be transferred to application).
Next we ran the interface program RWPOS_PARA_ENQUEUE and saw the message that the IDoc was fully posted. However, when we checked it in WE02, we saw the IDoc had actually failed. In WPER, we saw the error message:
u201CFI/CO Interface: Line items created several times.u201D
We double clicked on the error message to bring up the following diagnosis:
FI/CO interface: Line item entered several times
Message no. RW014
Diagnosis
The following document information was transferred several times:
*Reference document "U0000001M8"
*Reference organization ""
*Item number "0000000001" .
System Response
The document information keys must be clear.
Procedure
This is a system error of the application which was called up.
I drilled down to the SAP code trying to find what condition triggered this error message. The only place where this message is called is in the include program LRWCLF01, inside the subroutine CHECK_ITEMS. It seems that the system doesn't like the repetition of the item numbers in the IDoc. We consulted a functional consultant to see if we should change the second pair of items 1 and 2 in WPUF to 3 and 4. His answer was no.
We would like to get the expert advice from this forum to help us solve this problem. Your time and effort will be appreciated.
Thanks,
Ning
Edited by: Ning Hu on Aug 22, 2008 2:45 PM
Edited by: Ning Hu on Aug 22, 2008 2:50 PM

Just a guess, instead of
Item __ Acc.assgnt obj. ____ Cost Ctr __ Amount __ Crcy
1________________________7110150____100______USD
2________________________7110150____100______USD
1________________________7110150____200______USD
2________________________7110150____200______USD
try:
Item __ Acc.assgnt obj. ____ Cost Ctr __ Amount __ Crcy
1________________________7110150____100______USD
2________________________7110150____100______USD
3________________________7110150____200______USD
4________________________7110150____200______USD
Rob

RRI using Tcode in source system giving error

Hi,
I am trying to run a report in BW in tcode RSRT using RRI mechanism and the same is throwing an exception - An error occurred with the report to report interface during the jump. The same when run in BExAnalyzer throws an error "A critical error occured".
The selections I have applied are as under:
Target system -> Source System(ECC)
Report Type -> Transaction
Report Destination -> ME2L
Assignments as under:
0DOC_NUM -> EBELN
Any trace to the cause of the error would be helpful.
Thanks,
Amogh

Try creating a program in source whihc calls t-code ME2L and then from RRI try to call the program., and also check if you have authorization to t-code RSRR_WEB &RSBBS_WEB in you source system,
If this did not help give us more detial on the error you are faceing.
Shashi

While deducting customers TDS , system giving error.

Dear Friends,
1)We have made AR invoice .Its customer is TDS applicable.
2)While adding AR Invoice ,we have not added withholding tax.
3)Incomming payment of that invoice- for this entered TDS cut amount.
But when we add it. system does not post TDS JE(that is additional) as well as gives error "
Transaction without amount"
SAP B1 2007 PL12 ,TDS4.9
BR,
Mahesh.

Hi Mahes,
I have also faced the same issue in Incoming Payment. Even in there latest patch (5.3) also this is not corrected. I have rasied a message to Citixsys. will update you after i get reply from them.

CONF21 Inbound Idoc - How to Monitor the Error

I have just set up the idoc conf21 - and everything works perfectly well (I ticked "immediate update" via CI41 in order to avoid using CIP2).
I have simulated an error in the ILE01 unit of measurement I putted 'XXX'.
I launched the idoc via we19 and the idoc appears in status 53 green. ( This is normal because the status 53 represents only the fact that function module KK2A_GET_DATA_FROM_IDOC has runned without errors. It does not report errors possibly occuring in PROCESS_CC2_MESSAGES_PARALLEL.)
Obviously due to the 'XXX' the confirmation did not happen. The record disappeared from the table RUECK.
Question : How can I monitor this type of error ?
Thanks
Philippe

Go to CO16
reprocess - change the *** in unit of measurement to H
back - the line shoulb be green now
save
and up this is it !

Newly instlled system giving error while creating GL

Dear all,
While I am trying to post GL I am getting error;
"Msg No F1030, Functional module FMFK-FIKRS-READ"
Parameters;
"IP_FIKRS_FMA_OBJNR"
Can any body suggest me how to rectify this problem.
Regards,
NSB

Can u explain it..and Text of Error.

Creating inbound idocs in the same system

Hi
Could you please let me know the Steps i should follow to get the following req done?
Iam creating INBOUND IDOCS from flat file ...so my sending and recieving systems are same...
In WE20 i have setup the logical system and assigned inbound parameters with message type and proces code.
Iam using IDOC_INBOUND_ASYNCHRONOUS to create the inbound IDOCS but iam getting the error
EDI: Partner profile inbound not available
It looks like iam missing some settings here..
Please let me know what checks i need to make sure to get rid of this error and post the idoc.
Thanks
Govi

Hi,
You need to create the partner profile in WE21 - Type Port.
You need to give the directory name and the inbound file name. Just do the access test available to check if the file is accessible.
Also create the process code in WE42 and maintain the processing FM.
Hope this helps you
Regards
Shiva

Error in Inbound Idoc trigering Workflow Scenario

I am getting below Error while I am posting Z Inbound IDOC in production system.
Please tell me what is getting wrong and how to correct.
Work item 000000000000 cannot be read
Message no. WL803
Diagnosis
The work item with the specified ID can either not be read completely or partly (for example, its container).
System Response
The action was cancelled and the work item, if it still exists, set to error status.
Procedure
Check whether the work item has already been deleted or whether only parts of it can no longer be read.
In the latter case, the work item is inconsistent.
Refer to your workflow system administrator.
Points will be surely given to helpful answers.
Regards
Edited by: Tushar Mundlik on Feb 12, 2008 8:15 AM

Hi Krishna,
First we have to find out if the error comes from processing in the application or from one of the checks performed before the application is called.
Go to function module IDOC_INPUT_OPDERS and put a breakpoint on "PERFORM edi_mode_to_mem.". Then reprocess the Idoc and when the program stops at your breakpoint set INPUT_METHOD to 'A'. In this way your order will be processed online (using BDC and you can find the error).
If the program doesn't stop at your breakpoint the error comes from one of the checks before.
But please try this first and come back if this doesn't solve your problem.
Kind regards,
John.

Error Loading Hierarchy Error when updating Idocs in Source System

Hello Friends,
I am loading hierarchy data using Info pac into 0FUNDS_CTR . I have selected a hierarchy under hierarchy selections tab in the Info pac .
All Partner profiles in WE20 seems OK . But When I loaded data , throwing errrr message as below
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
When I checked in TC WE05 says that IDoc: 0000000000355113 Status: Error during syntax check of IDoc (outbound) with status 26 .
Please advice .
Many thanks

Hi Krishna4bi,
Actually we will monitor idoc status in BD87 in SAP BI As well ECC , while extracting the data from source sytem if any idoc struck we will manually process in BD87 , But you are telling that while loading the datasource the error occurred , so please check once in ECC side . Otherwise see how many packets are still process, make it red that infopackage and do manually update.
Hope it helps,
By,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://bluemarlinsys.com/bi.

Inbound Idoc in XI system giving error 56.

Similar Messages

Maybe you are looking for