Change INBOUND Idoc E1CSKSM

Dear experts,
I am new to IDocs. I have an Inbound IDOC to my HR system for creating cost centers. I have a field in the IDoc which is not present in my HR system. I need to remove it from the IDoc and then post it. How should I go about this?
The IDoc details are,
Basic type -- COSMAS01.
Message type -- COSMAS
Segment type -- E1CSKSM
|__ E1CSKTM
Thankyou!
Regards,
Sumit Nene

The missing field is "Cross sytem Business area" - GSBER
error--
No business area has been assigned to cross-system business area XYZ
The fact is we do not have "Business Area" defined in our system, but the inbound IDoc has this field. So this error is given.
If I create a Business area in my system and assign it to the incoimg Business area from Idoc, the Idoc gets posted.
My basic question is..
Do I create a Business area in my system and assign it to cross system business area or--
Ask the Idoc sender to remove it from the Idoc itself?
Sumit

Similar Messages

Change inbound IDoc 860 overlay the old text with new text

Currently whenever change inbound IDoc 860 gets posted new text gets appended. My requirement is: old text needs to be overwritten with new text. Can you please advice
Thanks

Hi Hock,
thanks for your answer. Unfortunately i think your are right.
Yesterday i got an answer from debopriyo mallick, does anyone know,
why this answer is dissapear?
Regards, Dieter

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Inbound IDOC user exits

Re: IDOC User Exits
Posted: Aug 1, 2006 10:43 AM        Reply      E-mail this post
Hi
I have a basic doubt. We can modify or add new segments and change existing values to segments only for outbound idoc.
I have a requirement where a particular field in a segment would be empty for an inbound idoc. Is it possible to change inbound idoc values after the idoc is created and before it gets posted.
Please let me know,
Regards,
B.Anandh

Updating IDoc data in segments.
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                OTHERS                  = 3.

How to change field values AFTER Inbound IDOC Posted successfully

Hi SAP Experts,
In my project I receive the inbound IDOC PORDCR05 from PI and posted as an Purchase Order in ECC.
I create the Z process code and Z function module (which is a copy version of IDOC_INPUT_PORDCR) and complete all the necessary configuration steps. It works perfectly.
My problem is: I have to collect some inbound idocs (that satisfied some criteria) and change the value of field EKPO-TXJCD and EKKN-KOSTL of the PO AFTER it posted successfully (means the purchase order is created and save in database).
How can I do this? I've try to put the logic code in Z function module, but it does not work, since at that time, the Inbound IDOC is not updated to the database yet.
Aprreciate your advise.
Regards,
Elaine.

Hi Elaine ,
as per your cretiria pick the idocs and take created PO# from status 53 & use the BAPI (BAPI_PO_CHANGE) to change the neccessary values in the PO. We can't reprocess those idocs again.
Reddy

Inbound Idoc Create/Change Purchase Order

Hi All,
I have to do a inbound Idoc scenario for create as well as change Purchase Order.
Which is the IDoc type for Create/Change purchase order.
I went through this form found that ORDERS05 can be used but I am not sure this can be used for both create as well change Purchase Order.
If ORDERS05 can be used then which is Process code,Function Module and Message type for both create and change Purchase order.
I also found that IDoc type PORDCR102 can be used for create Purchase order and PORDCH02 can be used for change Purchase order,but i don't want to use two Idoc types.
Please suggest.
Thanks in advance.
Regards,
John

Hi John,
For creating a IDoc for PO, whenever a PO is created/Changed, it has to be configured in Parter Profile(WE20) for a particular Partner in Outbound Paramtrs tab.
Give ORDERS05 in Message Type and select the line & go to Display.
In the screen which appears , choose tab Message Control and give the Process code
ME10 - Creation of PO
ME11 - Changes to PO & check the Change Message.
Give respective Output Message Type & Application(VF) for PO.
Create Output types for a vendor in T.Code MN04, else take help from MM Consultant.
Create a PO & save. Then make some changes in Po & again save.
Now IDoc will be created while saving the Po & IDocs will be created whenver you make changes to PO and saving it.
Hope It helps.
Regards,
Anbalagan

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

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

Change sales order values from Inbound Idoc

Hi all,
     In my scenario i have to change sales document automatically(Workflow) by getting the values from the inbound idoc ordchg (one more thing i dont want to create another sales document). Is there is any function module? please tell me how to do this.
Regards,
Adithan S.

Hi Adithan;
   You can read the IDoc information using the function IDOC_READ_COMPLETELY as demonstrated in the example below:
DATA: int_edidd TYPE STANDARD TABLE OF edidd WITH HEADER LINE,
       wf_docnum type edidc-docnum.
MOVE: 'IDOC_NUMBER' to wf_docnum.
CLEAR int_edidd.
REFRESH int_edidd.
CALL FUNCTION 'IDOC_READ_COMPLETELY'
     EXPORTING
          document_number         = wf_docnum
     TABLES
          int_edidd               = int_edidd
     EXCEPTIONS
           document_not_exist      = 1
           document_number_invalid = 2
           OTHERS                  = 3.
   After that call, you can loop through int_edidd to get at the segment information you need.
   You can update the sales order using BAPI_SALESORDER_CHANGE. Below is an example of updating line 10 of a sales order with a new material number.
DATA: l_vbeln LIKE bapivbeln-vbeln,
      so_headx TYPE bapisdh1x,
      change_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
      so_item_in TYPE bapisditm OCCURS 0 WITH HEADER LINE,
      so_item_inx TYPE bapisditmx OCCURS 0 WITH HEADER LINE.
MOVE 'U' TO so_headx-updateflag.
MOVE <insert sales order number here> to l_vbeln.
MOVE: '00010' TO so_item_in-itm_number,
       'MATERIAL_NUMBER' TO so_item_in-material.
APPEND so_item_in.
MOVE: '00010' TO so_item_inx-itm_number,
      'U' TO so_item_inx-updateflag,
      'X' TO so_item_inx-material.
APPEND so_item_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
     EXPORTING
          salesdocument    = l_vbeln
          order_header_inx = so_headx
     TABLES
          return           = change_return
          order_item_in    = so_item_in
          order_item_inx   = so_item_inx.
Cheers,
John

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

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

Inbound IDOC (change to delivery qty)

Hi,
I need to setup an inbound idoc to R3 which will change the delivery pick quantity. What is the idoc to be used and how to use it for changing the delivery pick quanitity for the already created delivery in R3
appreciate your help.
P.S

reopened a thread in ABAP Development » ABAP, General

Changing internal order's via Inbound IDOC

Hi,
      We are having Inbound interface set for creating internal order's using message type 'INTERNAL_ORDER_CREATE01'.
       But when any existing internal order is changed it is giving status 51 with error 'Order already exists'.
      I am wondering how can we handle the changed order situation via inbound IDOC . Is it possible to do it via message type 'INTERNAL_ORDER_CREATE01'.
Regards,
ganesh

Hi ganesh,
The idoc Status 51 for indound idoc is....
51 Application document not posted
the possible solution is checkthe Partner profile for the Idoc and Port number..
and go to T_code we20 and check the Partner.and check the Syntax in the application tool bar...
then you will come to know the problem..
and if you wan to changed order situation via inbound IDOC , yes it is possibel.
go to t-code we57 and check the Function module attached to the message type .
and go to FM and find hte customer exit and read the segment which contains order situation and modify the segment..
i hope this will solve the problem..
Regards,
Prabhudas

Database error changing table ADR2 - Inbound IDOC Create Order

Hi experts,
I have a backgroud job for program RBDAPP01 to process inbound IDOC message type OILLDD. It woked perfectly for years. Few days ago, the job got short dump and cancelled. In Error log, it shows error MESSAGE_TYPE_X Database error changing table ADR2 in function module ADDR_SAVE_INTERN.
I already try to activate trace log to see sql statement but still couldn't find anything suspicious. Have anyone been through this problem before? Please suggest.
Regards,

Hi,
Please check if this SAP note is useful. 1300825
Regards,
Srini.

How to trigger outbound IDOC when data changed in BP through Inbound IDOC.

Hi,
    In our system whenever we create a new Business Partner, these data is send across to SAP R/3 (as BDOC) and to Mainframe system (as outbound IDOC). Whenever we change any Business Partner record the data is send across to SAP R/3 (BDOC) and to Mainframe system (as outbound IDOC).
    This functionality is working fine.
    Currently we are getting a value for one standard field (Customer_Group3) of Business Partner as an inbound IDOC. The value of the inbound IDOC is reflecting in the field (Customer_Group3) in Business Partner Transaction. Once the inbound IDOC is received, the modified value is send across to SAP R/3 as BDOC. But the modified value is not send across to Mainframe system (outbound IDOC). The outbound IDOC is not getting triggered.
Kindly help

Is your mainframe system configured as Site in SMOEAC. If so are you using XIF Adapter.

Change INBOUND Idoc E1CSKSM

Similar Messages

Maybe you are looking for