Problem with outbound idoc

Hi guys,
How will I know the program that processes the outbound idoc given the mess type, basic type and extension?
Thanks!

Go to WE57 for assignment of FM to Basic idoc type, extension & message type.
If it is change pointers, then check BD50 & Bd61 & run RBDMIDOC, in this there an fm
    CALL FUNCTION tbdme-idocfbname
           EXPORTING
                message_type       = mestyp
                creation_date_high = date
                creation_time_high = time
           EXCEPTIONS
                error_code_1.
Check the value in "tbdme-idocfbname".
Regards
Kannaiah

Similar Messages

ECC 6.0 upgrade problem with outbound idocs

We are currently in the process of upgrading from 4.6C to ECC 6 and have found that our outbound idocs that use to process immediately are now pending in status 30. Message type DEBMDM is one of the several outbound messages that has the issue. Any ideas of what may have changed between 4.6C and ECC 6 that may have caused this to occur?

Hi Boss,
This problem is with Upgrading only . so, i can give two solutions for this .
1. create Background job with RSEOUT00 Executable program
and give the time like 2 min or 5 min (your choice)
2. check your code like includes in that code call the two Function modules that is DB_COMMIT
DEQUEUE_ALL
Try with this,,,,,,,,,,,,,
Best Regards,
Narasimha Rao.

Error handling problem with outbound idoc status 02 and XML HTTP Port

I set up an ALE scenario to send master data out of SAP via an XML HTTP port. All goes well until the idoc receives error 02.
It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques. Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
Is there any solution to still use the standard ALE error handling ?

Hi Karin,
Looks like based on note 701597, you can only reprocess these idocs manually via a workitem. I qouted the relevant text below:
3. Error handling with status '02':
An HTTP IDoc in status '02' should not automatically be sent once again.
Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
However, this report was adjusted and now deletes all IDocs in status 02
to be routed to a HTTP port from the list of selected IDocs. IDocs to a
HTTP port in status '02' should only be sent manually via a work item.
Regards:
Rex

Problem with Delivery IDOC staus 51

Hi all,
I have problem with Delivery IDOC.
An IDOC is sent from the logistics provider with reference to a manually created delivery, which creates another IDOC & another partial delivery.
The second IDOC created then confirms the partial delivery created by the first IDOC.
When IDOC try to confirm this delivery, it goes to status 51 with error " Delivery does not exist".
In some case IDOC was correctly processed & confirmed the delivery.
In some cases it went wrong.
Any ideas regarding this?

Hi Suneel,
It seems there is timing issue between the first IDoc and second IDoc.
When the first IDoc has not yet commit to DB then the second IDoc tries to process with reference to the first IDoc.
Is there any that can distinguish between 1st and 2nd IDocs?
In other word, can you post the second IDoc within minutes delay?
Just my two cents.
Regards,
Ferry Lianto

Problems with multiple idocs in one file ( Inbound file )

HI,
Thanks in Advance for your suggestions.. Highly appreciated.
We have problems with multiple IDocs in one file.
We are using XIB ( Amtrix ) as Middleware to receive the files.
Curretenly When the file contains one IDoc then there is no problem. IDoc is created and everything is ok.
If file contains two IDocs ( for example two messages ORDERS and DELVERY ) then it is creating two IDocs but both IDocs contains ORDERS plus DELIVERY segements information. That is the problem. Some how SAP unable to differentiate the IDocs in the file.. But it knows that how many idocs are there in the file..because it is creating exact number of idocs.
We are using TRFC port ... Do I need to change it to File port..
When we have more than one idoc do we need set any parameter in the file ...

Thanks for the swift response. Always ideas are useful.
As of now , Middleware cannot split the file.
Thing is SAP is creating two Idocs with different message types. Problem is First IDoc contains ORDERS message type but also DELIVERY segments as well. Second IDoc with DELIVERY message tyoe but ORDERS segments as well... This is the problem... I think we are missing some field activation in file for EDIDC record.
As far as I know file port supports the number of IDocs in one file.. Hope TRFC port also supports that

Problems with sender IDoc scenario

hi experts..,
when i create message Interface for a Outbound Idoc my scenario is not working.
if i use idoc directly instead of message interface its working properly
And in Interface Determination if i gv interface mapping we are gting errors and without mentioning interface mapping in Configuration its is working fine
can any one explain me what is the reason for my two questions
thx in advance
john wesly

Hi,
I will explain one example by taking one IDOC
we have ORDERS05 Idoc and we are using the same Idoc for two scenarios
Scenario1 -
IDOC---File( FTP Server)
Scenario2----IDOC-JDBC
Now let us assume that we have configured two scenarios.
If we trigger the IDOC Orders05 from SAP R/3 means
1) The Idoc will be triggered and it will reach to XI.
Now your doubt is which Receiver will be take place and to be executed.
This time the problem my come or may not come, let it be like that.
If your requirement is like the above mentioned thing means
1) We can develop a single scenario like
IDOC-------File( FTP Server)
JDBC
Here what we have to do is when the idoc comes to xi we have route the Idoc to the particular receiver based on some condition in Receiver Determination
And one more thing is in mapping also if we have two mappings then we can use Interface determination based on condition which interface mapping to be execute.
I hope this clears yor doubt
Regards
Seshagiri

Problems with posting iDocs from MDM in SAP R3

Hi,
I am an MDM consultant, with limited knowledge about SAP R3.
We send material master data from MDM, via PI to R3 using iDocs.
We are having problems with posting MATMAS, and it seems the problems are with updating already existing materials.
In BD87 we get the following warnings:
The field MARA-ERVOE is not ready for input and was therefore not initialized
The field MARA-ERVOL is not ready for input and was therefore not initialized
The field MARA-FERTH is not ready for input and was therefore not initialized
The field MARA-KZGVH is not ready for input and was therefore not initialized
The field MARA-XCHPF is not ready for input and was therefore not initialized
With the last message being:
No changes made
I have checked the MDM syndicator, and none of these idoc-fields are linked to the MDM repository.
So they are syndicated blank.
If we try to resend the material, it is again stopped and in BD87 I see the same messages.
Please help me understanding how to solve these issues.
Thanks,
Thomas

Hi,
Please refer the below threads which talks about the similar problem
http://scn.sap.com/thread/3180116
http://scn.sap.com/thread/1374222
Generally the basic view of the material to be created first. Then the sales, purchasing and other views to be created.
There are few fields in the other views which gets values from the basic data view.
Regards,
Antony

Problem in Outbound IDOC

hi experts,
I having an issue with the OUTBOUND IDOC.
i am getting error status code as 37 - Error IDOC added incorrectly.
what does it mean and how to rectify it.
message type : debmas04
extension msg type: exdebmas.
looking forward for your replies

Hi,
Double click on the status 37, in next screen click on information button, it will give you some more details of the error segments.
then we can discuss on those errors.
Reddy

Problem with Inbound Idoc

Hi everybody.
I´ve got a problem with an inbound idoc. I've got a standard idoc INOTIF with an extension.
To receive this Idoc from external systema I´ve created a Z FM to process this idoc.
The problem is that when this idoc get to SAP the FM never is executed and the idoc appears with red flag and show me
the next error: No status record was passed to ALE by the application and the idoc is shown with the status 51.
¿¿How can I fix this??
Thanks a lot
Regards

hi
and also give the funtion type is function module in we57 and in BD51 give ur ZFM and give 1 in input.t field.
now you can see ur FM in WE42 under Identification field F4 value.
The FM which is created by you it should be in F4 help list fo field Identification in we42.
and give the Message type and Process code in we20 in inbound parameters.
i am sure this will work .
regards,
Kiran Jagana

Problem with ARTMAS idoc

Hi
I am working on an IS-Retail implementation and we deal with article master (similar to Material master). The idoc corresponding to this is ARTMAS.
The scenario is as explained below.
We have articles classified as 'generic' and 'variant'. One generic article can have many variants. eg. T-shirt can be a generic and its variants could be 'High neck', 'V-neck', 'round neck' etc.
The issue is : Whenever we make article master changes to the generic article and execute the tcode BD21 - idoc type for change pointers for ARTMAS, the articles whose info is changed triggers the outbound idoc which contains a segment ' E1BPE1MATHEAD' containing the details of generic and a number of segments 'E1BPE1AUSPRT' which contain the details of the variants associated with the generic,
When i changed any field in MM42 for a generic article, the idoc generated through BD21 contains the segments for variant articles also.
However, when the description field -MAKTX is changed for the generic article, the outbound idoc generated through BD21 does NOT contain the segment for the associated variants.
I need the outbound idoc to include the variant segments (E1BPE1AUSPRT) also when the Description of the Generic article is changed.
I have checked the table fields associated with ARTMAS and the field MARA-MAKTX is included in BD52.
Can someone throw some light on this.
Thanks in advance.

hi negender,
can u help me how u solved the issue,
thanx,
hari

Problems with sending IDocs into R/3 using BPM

Hi Vishnu,
as I have read the forum, you have experience with sending IDocs into R/3 from XI using the BPM.
Did you have problem, that this sending takes very long time?
My BPM splits the xml, sends IDoc into R/3 immediately, but the processing of the 2nd IDoc takes 6-10 minutes!
Do you have any idea, what could be wrong?
Thanx 4 answer, Peter

Vishnu, I was discussing this problem in another thread, but no helpful answer was sent, and I have read, that you have experience, so - just for explanation
Well,
yes, this situation is really strange.. New facts are:
when I send into XI XML, which is splitted in the BPM only into 1 IDoc, it is processed immediately. When I send there XML for 2 IDocs, the first is processed immediately, the 2nd starts immediately, but end of process is after 6-10 minutes, it depends... Then I tried to send there XML for 10 IDocs - and now attention please! 5 of them have been processed almost immediately, 5 of them after 8 minutes... The last test was with 16 items - 6 processed immediately, 10 after 10 minutes... And all these 10 minutes was my 4 processor XI box unavailable, with over 60% load... But finally the IDocs arrive!!
Any explanation???
This is really unbelievable situation!
Port name is SAPDEV, rfc destination DEVCLNT100
Actually, when I was creating the scenarion using the wizard and trying to add my communication channel(IDoc type) to receiver agreement, I got error - communication channel is not configured correctly, use another one. But somewhere I read, that I should create the receiver agreement manually. So I did.
To my BPM:
-receive MSG
-switch (but I'm testing only one branch now) - and the MSG message is always passed here, it's ok
-then I have transformation to MultiMSG (message with multiple DATA for multiple IDOCS)
-then comes the split mapping Multi2SingleMSG
-then ForEach Block with sending the Single MSG
this is the end of the BPM, and outside the BPM comes the mapping Single2IdocMSG and sending the IDoc into R/3
before I had the Single2Idoc mapping in the BPM, but thought, that this could be the bottleneck, so moved the mapping after the BPM... It didn't help...
So, what do you say?
Peter

Problem with HRMD_A06 idoc

Dear All,
I am using the IDOC HRMD_A06 for carrying out various operation on the available HR infotypes.Kindly go thru the below mentioned details for further insight of the problem
1.Scenario:
a.An interface to SAP HR system needs to be built
b.The interface will supply incremental master-data in
form of flat-files
c.An integration broker ,SAP XI will then convert the
flat-files to I-Docs and send I-Docs to SAP HR system
d.The I-Doc chosen for this purpose is HRMD_A.HRMD_A06
e.However this I-Doc is not supporting different
operations on incremental data like modify, delete etc
f.Further validations are also not being supported
g.Also segments for certain info-type records are missing
Example for Delete Operation mode:
Operation Delete: Delete existing infotype record
Expected Result: Only the particular info-type record, as supplied in the I-Doc should be deleted and not the entire personal number with all the info-types
Actual Result: The entire personal Number is deleted.
Is it that the Idoc behaves in this fashion or there is some other flag apart from OPERATION, which needs to be set.
Regards
Vinay

Hi Vinay,
Have you found a solution ?
Because I'm a similar problem by using IDoc HRMD_A06. I have not a segment E1P0021 when I delete the infotype 0021 on an employee. I have only its segment E1PITYP.
Regards
Mickael

Problems with sending IDOC via RFC from Unicode to NonUnic

Hello
I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
I have tried different options in sm59, but it didnt help.
Any ideas? The recipient system is rather old, version 4.0

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Is Reatil Problem in Outbound Idoc

When I process POS outbound idoc wpdtax01 it will give error msg Error in ALE service and it have status 29, who can I resolved that problem
can any method for reprocess POS outbound idoc
thanks
Amit Shivhare

Hi Amit,
You can reprocess POS Outbound Idoc using program RWDREPROCESS2
Bye,
Muralidhara

Problem with mass IDoc for Material Master

Hi All,
Can anyone suggest a solution to work with mass IDocs for Material master?
We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
Regards
Pooja

Hello Pooja:
The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
Hope this helps.
Regards,
Jorge.

Problem with outbound idoc

Similar Messages

Maybe you are looking for