Multi Mappng - different inbound idocs

Hi,
I have a requirement to map a single outbound message into inbound different idocs.
Source: Src_mesg1,
Target: Idoc1 and idoc2.
I am able to create Operation mapping with different inbound idocs.
But not able to create message mapping with different target idocs.
Please suggest .
Thanks
sneha

Hi,
>Cant i acheive the same through simple message mapping ? Single source message and multiple target idocs : Idoc1 and idoc2.
Not if that are different IDoc types, in that case you need BPM
Regards,
Udo

Similar Messages

Why does an Inbound IDoc no change and differs from an Outbound IDoc no?

Hi Experts,
This seems to be a basic question..! But can someone kindly clarify why an IDoc number gets changed when sent from one R/3 system to another R/3 system and how does this happen???
i.e., whenever an IDoc was triggered from R/3 system A to R/3 system B through XI/PI, the Inbound IDoc number (in system B) differs from the Outbound IDoc number (in system A)... Why does this happen and how???
Thanks in advance!
Br,
G@nesh

Hi Ganesh,
The IDOC numbers are always Unique,
IDOC can be generated in SAP system as a result of internal testing (WE19), or
can be posted from a non sap system (say PI).
So every time a new IDOC comes, it is assigned a new number to avoid confusion and also this plays a
critical role in the end to end testing and validation.
If you look at the control record of the IDOC you can see a element called DOCNUM. this stores to actual IDOC number.
from PI side you can use IDX5 and in ECC We02/05 to notice the idoc numbers.
Regards,
Srinivas

Goods receipt against process order with inbound idoc

Hi Experts,
We need to post good receipt against process order with movement type 101 and for By-product 531.
Can we use inbound idoc-WMMBID02,with message type WMMBXY to achieve this functionality?
Or please advise if we can achieve this from any other Idoc type.
We are getting below field values for external system
1. process order number
2.plant
3.material
4.quantity in unit of entry
5.unit of measure
6.storage location
7. movement type
8.Batch
Kindly advise how can we achieve this.
Best Regards
CS

261 and 262 are two different movement types INDEPENDENT of each other. I definitely know for the fact that SAP allows you to create a 262 without a 261. if you were to restrict it... you can disable access through a tcode for that mov. type 262 and ask users to use MBST to cancel any material documents created via 261 movt type.. that would ensure a smooth process

Issue while trying to create Sales Order from Inbound Idoc ORDER05

Hi All,
I am trying to create a sales order through an Inbound idoc ORDERS05 created out of a Purchase order. The header pricing conditions from the Purchase orders gets populated in E1EDK05 segment and this needs to go to the Sales order header conditions while trying to create the Sales order.
But when the fields are getting incorrectly mapped to the Sales order. Issue being, the segment E1EDK05-BETRG contains the condition value. But this fields gets populated to the KOMV-KWERT (condition value) screen field on the Sales order header conditions. But this should have got mapped to field KOMV-KBETR (Rate). If I look at the Purchase order, E1EDK05-BETRG is the field getting fetched from field KOMV-KBETR on the Purchase order. So this should have correspondingly got mapped to KOMV-KBETR on the Sales order as well.
This looks like a standard behavior. But if any of you have encountered this issue before please let me know if any Correction instructions are available for the same. If this some issue in Pricing conditions configuration, do let me know.

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

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.

Inbound Idoc - Date fields not getting saved

Hello,
I have created inbound idoc scenario in SAP. I receive Idoc from non SAP system to SAP system.
then data from IDoc is saved into different tables, for that I have written one function module (attached to process code)
One of the segments in IDoc type has date as a field. It is of type sy-datum.
When I receive Idoc in SAP only date fields are not getting saved in tables.
Is anything specific need to be done for date fields? please advice.

check which format you are getting into sap and make sure you are coverting in into required format.

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

How to trigger change documents based on inbound-idoc?

Hi experts,
Currently I'm working in on a project where I have to create an interface based on IDOCS. This is an interface for two SAP-HR systems.
If there are made changes in the dialog (gui) by a user, there will be created a change document, which can be displayed by report RPUAUD00. For the inbound-interface based on idocs it's important that there will also be created a change document in the system based on this idoc. We have tested this, but no change document is created.
Can anybody help me to solve this problem: "How to create a change document based on the inbound-idoc?"
Thanks in advance.
With kind regards,
Roy

Thanks for responding. First, I like the idea of defining an event, but I'm still stuck with how to trigger it. I looked at dynamically registering events, and maybe doing something where a click on the graph control registers an event for key presses on the vi. I'd still have to figure out out to terminate the key press event. Unfortunately, (actually it's a feature I like..) there are a number of different ways to complete typing in a scale change. I routinely use ctr-enter (habit from working on a laptop), though enter works fine, and clicking somewhere else is probably the most common method. I am not that familar with User Defined Events, so I may be overlooking something obvious here.
The graphs are a Bode Plot, with a seperate graph for RPM vs Phase Lag, and RPM vs Magnitude. I want them to always be plotted on the same x-axis. The plot is generated when the user doubleclicks on a dataset. After that, it's just the user looking at it. They can change the axis without any new data being generated.
Thanks,
Chris

Problem with HR inbound IDoc

Hi,
I have a problem with processing inbound IDocs from an external payroll system to infotype 0008. The process is quite simple; salary changes from the payroll system is recorded to the corresponding employee's infotype 0008. When testing I noticed that that the new record is recorded as is. For example if there is already an existing record with the validity dates 01.01.2010 - 31.12.9999 and the new record in the IDoc is 01.01.2011 - 31.12.9999, the new record is written as is. I would expect the system to delimit the old record correctly - similar to what would happen if you maintain records online. There is no error checking or any kind of processing done by the system.
I did some debugging and found out that the function module linked to process code HRMD writes the information directly to the database. If this is a standard way of doing this, it is really unusual.
Has anybody else encountered this? Any pointers?
Thanks.
Edited by: Theo Droste on Jan 20, 2011 11:56 AM

Hi
This is correct, the ale programme writes the data directly to the database, I have faced this isssue on occassion. I once raised an oss message on this as well, and sap confirms this is what happens. If it is a sap to sap ale, it somehow seems to work, - this could be because the outgoing idocs are created by sap itself but if it is a non sap to sap ale the onus is on us to ensure that the external system sends the correct data to sap in the way we intend it to be displayed.
that is how it has been in my experience. It is unusual, but apparently not impossible. Please let us know if you find out anything different.

Inbound IDOC status is strucked at 64

Hi,
My rerequirement is as follws.
Inbound IDOC process:
Through inbound IDOC i have to create the new sales orders and need to change some information to existing sales orders means 2 cases.
1) Create new sales order
2) Change existing order.
Iu2019ve generated two example IDOCs from order interface
one for an u2018order addu2019 and one for an u2018order changeu2019.
The times each IDOC reached each status are shown below:
IDOC 1677672 u2013 Order ADD
Status: 50 Started         Time:    09:54
            64 IDOC ready               09:54
            62 Direct Call                 10:39
            53 Order Created           10:39
IDOC 1677684 u2013 Order CHANGE
Status: 50 Started         Time:    12:50
            64 IDOC ready               12:50
            62 Direct Call                 12:50
            53 Changes on Y-table   12:50
Can anybody explain why the first IDOC had to wait for the scheduled
u2018IDOC PROCESSINGu2019 job to run, before it moved from status 64 to 62. But
the second IDOC appears to have been processed automatically without
waiting for the next run of the scheduled job?
Obviously, the u2018automaticu2019 processing of the change IDOC is the way we
would prefer it to work all the time).
Can any body explain in first case why it's taking time and in second case it's processed immidiately.
Regards,
Janardhan

Hi,
I believe you are using two different message types for this purpose. One to create order and one to change order. Did you check the partner profiles for these? May be partner profile(WE20) for creating order is set as "Collect Idocs" whereas the partner profile for the message type to change order is se as "Trigger immediately".
Hope it helps.
Regds,
Rudra

Inbound idocs segment fields

Hi,
Iam new to idocs and a functional consultant. I need to know whenever we receive the inbound idocs and if i see the segments of the inbound idoc, do the fields which i see in the segments are the sap fields.????/ for instance if the inbound idoc needs to create a sales order, then the fields of the segments of such an inbound idoc are the normal sap sales order fields ??
do i need to give functional specs to the abapers that whenever the inbound idocs is received the segments fields need to be mapped to sales order fields if such an idoc needs to create a sales order ??
regards
sachin

Hi Sachin,
Most of the IDoc segment fields are simmilar to SAP transaction fields e.g. most of the ORDERS IDoc segment fields will be simmilar to what you can see in VA01/VA02 screen fields.
Some fields may have different names.
In the case of few segments which may repeate in IDoc with different qualifiers (such as partner details, date segments), fields will be same but different qualifier value decides where these field values will be populated in the Order.
If you are using standard function module to create Order, it will take care of mapping IDoc segment fields to VA01/VA02 screen fields. But if it is a Z function module, then you need to specify the mapping.
Hope this information will help you.
Regards,
Mahesh Pakhale

Can Inbound IDOC create a BP(Business partner) In SAP CRM system

Hi
Req:
Contractor data is transfered from ERP system to CRM using Message type HRMD_ABA with ALE Distribution Model in place.
Inbound IDOC is Successfully Posted when checked in WE05 in SAP CRM System.
Question :
1. Can an INBOUND Idoc create BP automatically or is there need of Configuration or Any custom program .
Appreciate Your Response
Bhanu Polsani
Edited by: Bhanu Polsani on Oct 4, 2011 6:10 PM
Edited by: Bhanu Polsani on Oct 4, 2011 6:16 PM

You can maintain two different address for the business agreements (can be treated as mailing address for the printed invoice)but you can not maintain more than one standard address for BP as any given time.
Regards,
Sanjoy

Receiving error msg in user's mailbox for both Outbound and Inbound IDocs

Hi,
Whenever specific IDoc (Inbound/Outbound) gets failed then the user/org unit assigned in its partner profile should get those error messages in their inbox.
To achieve this for Inbound Idoc I have performed following set of steps:-
1. Created an object and attached it under IDOCAPPL using 'SWO1' and I have set that object type as 'To imported'.
2. I have assigned that object type to event 'ERRORINPUTOCCURRED' and standard tasks '00008068' (Inbound processing error), '00008074'
(Inbound Syntax error), '20000051' (IDoc Application Inbound error), '300000207' (Error during Inbound processing of SYSTAT01) using transaction 'SWETYPV'.
3. I have created an organisation unit with two positions and different jobs where each job has been assigned to specific tasks. User has also been assigned to specific jobs.
4. At the end of this I have assigned this org. unit to IDoc's partner profile.
But this process does not seem to be working we are not receiving any mail in agent's inbox. If someone has done similar kind of thing in past, please let me know the correct step for both Outbound and Inboud IDoc.
Thanks in advance.
Supriya

Hi,
Try this for inbound IDOC
Go to transaction WE42
Give the process code that you gave in the partner profile (WE20)
Select that row and press the details button (F2).
Next to the "Identification" field there will be push button which has the tool tip "ALE table"
Press that button
In the resulting screen..
In the IDOC section..
Give the following..
object type - "new business object that you created"
Start event - INPUTERROROCCURRED
End event - INPUTFINISHED
Hope this works..
Thanks,
Naren

Trigger an outbound idoc to sender system after inbound idoc has status 53

Hi all,
We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
Kindly help me in solving this issue.
Thanks,
Aravind

Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
& call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
Master_IDOC_CREATE, hope the solution works for you

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

Multi Mappng - different inbound idocs

Similar Messages

Maybe you are looking for