Inbound idoc ( shipment) - Status change

Hi Experts,
I will be getting an inbound idoc containing tracking number of the shipment from an external agent.
I have to update this tracking number in the shipment and change the status of 'shipment Start' and 'Shipment End' to be completed.
1. Is this status change feasible ?
2. If so can you please guide me both to update tracking number & status .
Thanks
Seema

Hi Martin,
Thanks for the response.
Can you tell me which basic type will suit for this among SHPMNT01 to 05. I need to get the tracking number from any of the segments.
thanks
Seema

Similar Messages

Inbound IDOC FINSTA01 status Change

Hi,
Actually we are posting in bound idco for lockbox using Idoc Finsta01,Depending on the header and item amount ,ie if both are not equal need to post the idoc with 64 status with custome message.
Any User Exit ?
Thanks,
Madhu

Hi,
Please check these user exits for IDOC_INPUT_LOCKBX.
EXIT_SAPLIEDP_201 (for Settlement Handling)
EXIT_SAPLIEDP_202 (for Segment Processing)
EXIT_SAPLIEDP_203 (for Changes to Payment Advice)
Again, you need to fill up structure parameter FIMSG with your custom message and raise an exception.
Regards,
Ferry Lianto
Please reward points if helpful.

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

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

Error in re-processing inbound idocs of status 51

Hi
We are facing problems in reprocessing inbound idoc from BD87 transaction
We have an inbound process code 'STA1' which is pointing to a standard task 'TS30000206'. we have an errored inbound idoc(status 51) of message type 'STATUS' ( standard status change idoc pointing to process code STA1 for a valid port. Whenever we try to process it using BD87 transaction, we are getting errors B1033-'No function module for input process code STA1'.
We dont understand what we were missing. When we try the same for a process code which points to a function module, BD87 reprocesses it correctly.
We tried adding an entry in BD67 with an inbound function module 'APPL_IDOC_INPUT1'. Note that we still had the process code pointing to the same task. This time BD87 reprocessed idoc, but gave 51 again saying that 'Function module not allowed: APPL_IDOC_INPUT1'.
Any pointers or help in this regard will be highly appreciated.

Hi,
Please check IDOC TYPE, MESSAGE TYPE & PROCESS CODE and also check the we30, we42. & try BD87 reprocess of an IDOC.

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

SAP JIT Inbound - The external status change you requested is not planned

Hi All,
I am getting an error as "The external status change you requested is not planned" while creating JIT call in JIT inbound.
I have configured actions and external status.
What would be the problem??
Help me
Thanks,
Anbazhagan

Hi Lakshmipathi,
Thanks for your reply.
I missed out some configuration. Now the issue is solved.
Thanks,
Anbazhagan E

Inbound idoc pordcr101 status 51 "enter purchase org"

in the we19 standard inbound for idoc pordcr101 i see the following
EDIDC with the partner/port info
E1PORDCR1
E1BPMEPOHEADER
    comp_code 300
    doc_type "NB"
    vendor 58121
    purch_ord 3000
    purch_group 000
E1BPMEPOHEADERX
    'X' next to respective fields
E1BPMEPOITEM
     po_item 00010
     Material scw1212
     Plant    3000
     qty       1000
E1BPMEPOITEMX
     'X' next to respective fields
Each time i run the inbound idoc pordcr101 in we19 with the above i get
enter purch org
i am really really stuck because i am entering purchase org but for some reason it does not know about it
what am i missing
HELP
I deleted the unused segments

no successful idocs in we19 up to this point
i was told
E1BPMEPOHEADERX 'X' next to respective fields this is used to indicate which fields are being input.
so i am using both
it is purch_org not purch_ord

WE-19 Inbound Idoc Process - Status Code 51

Hi,
I generated Outbound idoc COND_A successfully to send it out to XI. I used same Idoc again in WE19 and changed partner details and tried Inbound Processing. Its giving me error code 51 ("ISO Currency USD can not be converted unambiguously to SAP currency for E1KOMG" )
Any Idea how to fix this error. basically I did not changed anything.
Message was edited by: Ram Krish

Appana,
Thank you very much for your reply.
I did setup all parameters as Iam getting this Idoc as an Inbound to R3 as well. Thsi Idoc will be both Outbound and Inbound to R3.
I successfully sent this Idoc to XI. and then as I wanted to test the same Idoc for inbound, I changed Paramters according to my setup.
Sequence of status are
74 - created with test transaction
50 - Idoc added
64 - Idoc ready to be transferred to Application
62 - Idoc Passed to Application
51 - ISO currency USD can not be converted unambiguously to SAP currency for KOMG
I looked at several fields in E1KOMG segment and changed one of the currency field to USD which didn't help to fix this error.
I really appreciate any help to fix this error.

How to block the status mail for an inbound Idoc to a specific user

Hi,
I have to stop sending the error status mail to a specific user depenidng on Partner Type. This will trigger when an inbound Idoc contains status error(message type INVOIC &ORDRSP).This user needs other mails which are getting triggered with the same Idoc for the same partner. Basically, the requirement is to block only the status mail for that user. The statndard task for this is TS70008125 and it uses the agent determination rule 30000001 (Idoc Administrator).in WE46, this task is assigned to process code EDIR. I have copied the task to a custom task and changed the agent determination rule. I would like to know how will I configure this task so that this custom task will trigger for the status error, without altering other workflows for the same message type & the partner type. Or is there any other way to block the mail?
Thanks,
Santosh

Hi,
I have done the required coding to exclude the specific agent from the rule,copied the task and its ready. My question is how do I map this custom task to a particular partner type, for the message type INVOIC in WE20? (The message type used for the inbound Idoc is INVOIC). I checked the Partner profile in WE20. Most of the process code is using function module as the processing type.
Thanks,
Santosh

Inbound idoc with error status 52 messege type hrmd_a07

i have an inbound idoc with status 52
error messege : Object 01 ,P ,00056786 does not exist: infotype 0302 cannot be created
Object 01 ,P ,00056786 does not exist: infotype 0006 cannot be created
i debugged but i haven't find out the reason
am updating 0000,0001,0002,0003,0006 infotypes

Hi rahul,
Need to check the address filed (0006) for BP mapped to postion (00056786)
Infotype 0302 (Additional Actions) :
Infotype 0302 is not maintained directly and is automatically updated by Infotype 0000 .
The additional actions Infotype (0302) is of time constraint 3 (gaps and overlaps).
Specifically in some cases if we want to have a non status-changing Action on the same day where already a personnel action is existing at that time we can activate the Infotype 302 by executing Report RPUEVSUP.
please check and let me know . I think it will be helpfull
Thanks and Regards,
Krishna

Inbound Idoc segment change

Hi All,
How can We modify or append a segment to the inbound IDOC. The scenario is as follow
We have an inbound IDOC to create/change contract order. There are some segments in the IDOC to hold the error records.
while processing the inbound IDOC we need to fill these blank segments with relevant data, so that we can reprocess the IDOC with ease.
I am trying the modify the IDOC_DATA inside the processing function module. Till the end of the function module IDOC_DATA is having the added segment data, however when I am checking from WE02, the segments are appearing to be blank.
Please let me know, what is missing above.
Thanks & Regards
D. Pradhan

Which exit / BAdI are yous using for adding the segment & what is your inbound processing function module ?
Anyways i also had the same problem a few weeks back i was trying to delete a segement though
My understanding is in WE02 it displays the data from EDIDC & EDIDD. In your I/B processing FM you only modify the data in the IDOC_DATA table & not in EDIDD.
Check in EDIDD, the segment would not be there.
BR,
Suhas

Find the Inbound IDOC

Hi Experts,
I have a requirement to get the Inbound IDOC for particular PO. I have used the following method:
http://forums.sdn.sap.com/thread.jspa?threadID=1082790
That means using tables:
A) SRRELROLES
B) IDOCREL
This is working for most of the cases except if the inbound IDOC is amended by the sender ( ex:- requested quantity changed ).
1. If inbound IDOC received without any changes, it will be there in SRRELROLES as roletype = 'INBELEG'.
2. If inbound IDOC received with changes it is not there in SRRELROLES.
Could you please help me to resolve this issue?
Thanks,
Chaminda

Hi,
Thanks for your help.
anyway, finally i had to use the time consuming way as there is no any other way.
1. Get all the ORDRSP Idocs from EDIDC based on the selected date range
select docnum status
      into table lt_edidc
      from edidc
     where credat in p_date1 and
           mestyp = 'ORDRSP'.
    if sy-subrc eq 0.
      sort lt_edidc.
2. Get all segment data records for the control records
      select mandt docnum counter segnum segnam psgnum hlevel dtint2 sdata
        from edid4
        into table lt_edid4
         for all entries in lt_edidc
       where docnum = lt_edidc-docnum and
             segnam = 'E1EDK02'.
3. to imporve the performance, i have used BINARY SEARCH when search back the IDOC from PO.
Thanks,
Chaminda
Edited by: chamindakrat on Feb 17, 2012 12:07 AM

Aggregated IDOC partly Status 51

When dealing with aggregated inbound IDOCS the Status 51 can be seen about 10% of all Status- Sets for different reasons. The worst is: The Switchdoc is currently block by <TheRCFUser> (here having EDIFACT/UTILMD/E03)
After that the complete Message won't be processed any further.
Is there a way to easily restart this IDOC for those segments with Status 51 (or better: for all segments not having 53 so far).
Maybe with the option to change the IDOC- Data before reprocessing (in case there is some stupid mistake like , instead of .)
Anybody facing the some problem and having a solution?
Regards, Daniel

Dear Math,
Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
status 51 after status 53. Outbound delivery is updated but not the sales order.
can you please help me

Idoc at status 51, however outbound delivery created

Hi Gurus,
We have peculiar issue , where in outbound delivery is getting created through IDoc. The inbound idoc has status 51 however delivery got created. Any idea how is it possible?.
Thanks in advance.

Dear Math,
Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
status 51 after status 53. Outbound delivery is updated but not the sales order.
can you please help me

Inbound idoc ( shipment) - Status change

Similar Messages

Maybe you are looking for