IDOC : ORDRSP, Fucntion Module

Hi Experts,
We are using Message type ORDRSP and Basic type /AFS/ORDERS05.
Can any one tell me the name of Function module, which is used for standard outbound processing for the same IDOC ?
Regards,
Study SAP

Hi,
   you can use standard outbound process code SD10.
   which has function module of idoc_output_ordrsp
   for sale order confirmation.
regards
mahesh.

Similar Messages

IDOC : ORDRSP, Fucntion Module for debugging.

Hi Experts,
We are using idoc Message type ORDRSP and Basic Type /AFS/ORDERS05. As Outbound.
When we are creating this idoc by using (WE19) Test idoc tcode, it is not stopping in the function module J_4A_IDOC_OUTPUT_ORDRSP and IDOC_OUTPUT_ORDRSP.
We have putted External Brake Point in both the FM.
We are using the processing "Standard Outbound Processing"
Please help me to solve this problem,
Is there any mistake with Function Module where we are putting these breakpoints are not used during the process ?
It is really urgent,
Regards,
Study SAP

Hi, Inbound process code for WP_PLU message type -
WP_P.
reward pts if it helps...

SENDING WBS ELEMENT IN OUTBOUND IDOC ORDRSP

Hi Experts,
i need to update idoc ORDRSP (to distribute Sales order) with field WBS ELEMENT , you can find this under item tab "Account assignment" field COBL-PS_POSID
I generated outbound idoc on several sales orders but none of them has this information.
do you know how to have this information populated in this idoc ?
Thanks and regards

Hi,
You need to do the following steps to create a custom segment and populate values into that:-
1. Create a custom segment using the T Code WE31
2. Add the created custom segment to the orders05 basic type by creating a new extension using WE30 transaction
3. Maintain a new entry in WE82 transaction for the message type, basic type and extension
4. Update the extension in all the necessary partner profiles WE20
5. You have lot of function exits in the function module IDOC_OUTPUT_ORDRSP, you can see them as customer function in that function module. You need to write the code in that include
6. Create a project for the function exit and activate the project.
Once you do all the above 6 steps then you can see values populated into the custom segment.
Thansk,
Mahesh.

Sales Order no and IDOC No Link table for Sales Out bound IDOC ORDRSP

Hi Friends
How to find Sales Order no and IDOC No Link table for Sales Out bound IDOC ORDRSP.
Thanks in Advance.
SR

Hi
If the idoc is managed by message, the link are stored in GOS (Obeject Service)
U can try to use the function module NREL_GET_NEIGHBOURHOOD
If you put
IS_OBJECT-OBJKEY = <sales document>
IS_OBJECT-OBJTYPE = <business object> (I think BUS2032)
the function returns the idoc
or if you put
IS_OBJECT-OBJKEY = <idoc number>
IS_OBJECT-OBJTYPE = <business object> (I think IDOC)
the function returns the sales order
You can investigate that function module in order to find out the tables
Max

Non-po invoice posting using IDOC into LIV module

Hi,
does anyone know if idoc interface is available for posting non-po invoice as an LIV invoice into MM module. what I found that I can post the idoc to FI module directly using message code - FI.
Thanks.

Hi
I Got your name from this site.I would be very thankful if you can help me here.I am designing a EDI based invoice LIV.Is it possible to post some charges which are without PO reference but are coming in Vendor Invoices.Is it possible to post these kind of charges with EDI message INOIC01 or we have to post through FI posting.If possible through EDI in which segment of IDOC we will enter these charges with amt.Also is it possible to post credit memo also with EDI
Thanks
Sanjeev

Error in Message Mapping "Target message IDOC: ORDRSP.ORDERS02 does not exi

Hi,
I have joined newly to the team.
When I tried to open one message mapping it throwinf follwing error...
"Target message IDOC: ORDRSP.ORDERS02 does not exist in software component version ID: 44423362454456485465..
Check whether the software component version ID: 44423362454456485465 is in Enterprise Service Repository. Import this version if necessary"
Is there any impact because of which in the message flow?
In my case some of the messages are failing with mapping error "runtime exception occured during application mapping com/sap/xi/tf/_SUS2MMOrderResponse_; java.lang.NullPointerException: while trying to invoke the method java.util.Map.get(java.lang.Object) of an object loaded from field com.sap.aii.map`"
And some of the messages are processed sucessfully and they also using the same mapping program 'SUS2MMOrderResponse'.
Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
Regards
Baskaran K

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

Outbound IDoc ORDRSP to XI

Hi Friends,
At present outbound IDoc ORDRSP is used in Customer EDI feed.
Based on my requirement I have to route this outbound IDoc ORDRSP to XI based on the Plant XYZ1.
Any customizing need to be done or Customer Functions need to be changed. Please guide me to know how to do this.
Thanks in advance.
Regards
Suresh

Done by customizing

Create Return Order via Fucntional module

Hi all,
I am trying to create a return order with refernce to invoice via fucntional module SD_SALESDOCUMENT_CREATE
In SALES_HEADER_IN, I am giving REF_DOC - Invoice number, REFDOC_CAT - M
In SALES_HEADER_INX , I am putting X mark for the above fields
I am Passing necessary details with material.I see the return order is created succesfully, but the invoice number is not updated in Accounting tab - Reference fields - Header.
Please anyone help me if the values what I have passed is correct or not to create the return order via Functional module
regard
Mano

Hi Mano,
Could you please upload screenshot of the field you are referring to
thanks
santosh

Need help for IDOC inbound function module !

Hi guys please help me to create a IDOC inbound function module.
What are the parameters and tables.
How to write the code.
What it does.
Please send me one inbound func module code if possuble
Thanks

Hi,
You need to create an inbound function module. Then define the process code in transaction we42 and attach the function module to this process code.
In the function module you create you need to define tables of types EDIDC (Control record (IDoc)), EDIDD (Data record (IDoc)) and BDIDOCSTAT (ALE IDoc status (subset of all IDoc status fields)).
Regards,
Soumya.

Set PO item rejection indicator via IDoc ORDRSP?

Dear experts,
is it possible to set the rejection indicator in the purchase order item (EKPO-ABSKZ) via processing an order confirmation IDoc ORDRSP?
I found nothing but SAP note 890812 where SAP proposes a workaround with manual setting of the rejection indicator.
Our scenario is that the vendor sends an ORDRSP Idoc with action code 001 in segment E1EDP01-ACTION and a sales blocking reason in fields E1EDP01-ABGRU and E1EDP01-ABGRT. We already found a way to ignore segments containing these fields and process all other IDoc items, but it would be nice to set the rejection indicator automatically for these rejected items.
We are on ECC 6.0 SP06.
Any help is appreciated.
Kind regards,
Karsten

do you really want your vendor to decide if you have a request or not?
dont you need this reopened requisition to procure that material at the vendors competitor?
by the way,
The corrosponding purchase requisition is opened again and new PO's are created by MRP.
MRP never creates POs. MRP can create requisitions. But why should MRP do this in case your PR is reopened instead of deleted?
You should rethink about this statement.
MRP will probaby recreate the requisition if you would close the requisition with the Order response from your vendor, so why not reusing this PR instead of deleting and crating a new one?

Send Changes for IDOC ORDRSP

Hi Gurus
Can anyone help me in sending the changes for the IDOC for transactional data.
For Sales Order IDOC -- ORDRSP.
When newly sales order is created, all the sales order information should be sent. --This is not a problem.
When changes are done on the sales order -- Only the changes should be sent in the IDOC. I have activated the change pointers in BD50, BD51 for ORDRSP and in BD52 created the entries for ORDRSP.
but when i trigger the IDOC using the output type, i get to see all the data instead of only the changes.
Is there anything that i am missing???
Any help is really appreciated.
Thanks
Saritha

Hi Linda,
I have documentataion on ALE/IDOCs which may not be helpful to you. If u need that i can send u .
Instead i can help u out if u r facing any issue.
In our case: wen ever sales order is created /changed an idoc shud be genrated.
This can be done thru Message control.
Which involves customization from functional guys in NACE as well as Technical guy in Partner profile/port..
do let me know where ever u r not clear.
regards,
Naveen

Inbound IDoc Posting Function Module

Give me an example of   how to write "Inbound IDoc Posting Function Module".
In my IDOC i have 10 segments each containing 1 field.
How do i create the Inbound IDoc Posting Function Module ??
Is the following code correct ??
FUNCTION ZIDOC_INBOUND.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
*DATABASE TABLES
TABLES:LIKPUK.
*DATA DECLARATIONS
    DATA: SALES_ORDER_NUM             LIKE Z1VBELN.
    DATA: DEL_TYPE                    LIKE Z1LFART.
    DATA: ACTUAL_GOODS_MOVEMENT_DATE LIKE Z1WADAT_IST.
    DATA: SHIPPING_POINT              LIKE Z1VSTEL.
    DATA: LOADING_POINT               LIKE Z1LSTEL.
    DATA: ROUTE_PGI                   LIKE Z1ROUTE.
    DATA: PICK_DATA                   LIKE Z1KODAT.
    DATA: CUST_NO                     LIKE Z1KUNNR.
    DATA: LOCAL_DATE                  LIKE Z1STDAT.
    DATA: TOTAL_GOOD_MOV              LIKE Z1WBSTK.
*INTERNAL TABLE DECLARATION
DATA:
IT_LIKP LIKE LIKPUK OCCURS 0 WITH HEADER LINE.
INITIALIZE WORK FLOW
    WORK_RESULT = C_WF_RESULT_OK.
     LOOP AT IDOC_CONTRL.
MAKE SURE WE HAVE CORRECT MESSAGE TYPE PASSED.
     IF IDOC_CONTRL-MESTYP NE 'Z_IDOC_PGI'.
     RAISE WRONG_FUNCTION_CALLED.
     ENDIF.
CLEAR APPLICATION BUFFERS BEFORE READING NEW ENTRY
    CLEAR :IT_LIKP.
REFRESH IT_LIKP.
*PROCESS ALL THE DATA RECORDS IN AN IDOC AND TRANSFER THEM TO
*APPLICATION BUFFERS
INCLUDE MBDCONWF.
LOOP AT IDOC_DATA WHERE DOCNUM EQ idoc_contrl-docnum.
CASE IDOC_DATA-SEGNAM.
WHEN'Z1VBELN'.
   SALES_ORDER_NUM =    IDOC_DATA-SDATA.
   MOVE-CORRESPONDING SALES_ORDER_NUM TO IT_LIKP.
WHEN 'Z1LFART'.
   DEL_TYPE    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING DEL_TYPE TO IT_LIKP.
WHEN 'Z1WADAT_IST'.
   ACTUAL_GOODS_MOVEMENT_DATE    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING ACTUAL_GOODS_MOVEMENT_DATE TO IT_LIKP.
WHEN 'Z1VSTEL'.
   SHIPPING_POINT    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING SHIPPING_POINT TO IT_LIKP.
WHEN 'Z1LSTEL'.
   LOADING_POINT   = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING LOADING_POINT TO IT_LIKP.
WHEN 'Z1ROUTE'.
   ROUTE_PGI    = IDOC_DATA-SDATA.
   MOVE-CORRESPONDING ROUTE_PGI TO IT_LIKP.
WHEN 'Z1KODAT'.
   PICK_DATA =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING PICK_DATA TO IT_LIKP.
WHEN'Z1KUNNR'.
   CUST_NO =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING CUST_NO TO IT_LIKP.
WHEN'Z1STDAT'.
   LOCAL_DATE =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING LOCAL_DATE TO IT_LIKP.
WHEN'Z1WBSTK'.
   TOTAL_GOOD_MOV =   IDOC_DATA-SDATA.
   MOVE-CORRESPONDING TOTAL_GOOD_MOV TO IT_LIKP.
ENDCASE.
ENDLOOP.
selecting data from the database
select * from likp into corresponding fields of table it_likp.
add status record
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = it_likp-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = it_likp-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LFART.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LFART.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WADAT_IST.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WADAT_IST.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-VSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-VSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-LSTEL.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-ROUTE.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-ROUTE.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KODAT.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KODAT.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KUNNR.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-KUNNR.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = SY-DATLO.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = SY-DATLO.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WBSTK.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = IT_LIKP-WBSTK.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
endloop.
endfunction.

Hi,
First goto WE20-> click on the logical system , now select the receiver LS which you are using as your partner. Now in the inbound parameters cehck what is the process code is attached.
once you get the process code then go to WE42 tcode.. there you give the process code and then double click you will get the function module IDOC_INPUT_FIDCMT.
Hopw you got my point.
Regards,
Nagaraj

Creating a custom IDoc inbound function module

I have created a custom idoc.I wanted to create a custom IDoc inbound function module, this Function module will provide to launch a BAPI .Tell me how to "create" inbound function module for the custom idoc ?

Goto any standard for the Paramtetres
*" IMPORTING
*"     REFERENCE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     REFERENCE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     REFERENCE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     REFERENCE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     REFERENCE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     REFERENCE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*"     REFERENCE(DOCUMENT_NUMBER) LIKE VBAK-VBELN
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*"      EDI_TEXT STRUCTURE EDIORDTXT1 OPTIONAL
*"      EDI_TEXT_LINES STRUCTURE EDIORDTXT2 OPTIONAL
Do the below configs.
1.Recognise the funcmod as Inbound -BD51
2.Register the Function module in WE57 .
3.we42 Process code .
4. WE20 -PARTNER Profile
I hope it resolves ur Query.
Rgds
Sree M

IDOC inbound function module!

Has anybody worked on IDOC inbound function module !
What is the meaning of the following steps !
IDOC_STATUS-DOCNUM = IDOC_CONTROL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-MSGTY = 'E'
IDOC_STATUS-MSGID = ' ZE'
IDOC_STATUS-MSGNO = '007'
IDOC_STATUS-MSGV1 = IT_LIKP-vbeln.
APPEND IDOC_STATUS.
What are possible values for MSGTY,MSGID, MSGNO.....
What do they mean !
Edited by: Alvaro Tejada Galindo on Mar 10, 2008 7:18 PM

"here nothing complicated ...
"status 51 means 'Application document not posted'
"in WE02 you can see this message
IDoc: 0000000000001254 Status: Application document not posted
IDOC_STATUS-DOCNUM = IDOC_CONTROL-DOCNUM. "IDoc number
IDOC_STATUS-STATUS = '51'.                                      "stauts code
IDOC_STATUS-MSGTY = 'E'                                         "error type
IDOC_STATUS-MSGID = ' ZE'                                       "message class ID
IDOC_STATUS-MSGNO = '007'                                     "message number in ZE
IDOC_STATUS-MSGV1 = IT_LIKP-vbeln.                      "document number or order number
APPEND IDOC_STATUS.

Copy Standard Fucntion module

Hi,
I am copying the standard fucntion module in R/3. My requirement is i would like to make changes for standard and create the generic. I am getting the Interface error for the function module while copying as it has related Type Group. Can anyone help by providing me the inforamtion how to copy type group for this function group.
Thanks

Sorry, it cannot be an acesskey information because i am copying. It cannot be an authoriation as i have the developer access.
It is the Function Module -> improt tab for the standard function module , they have used type groups which is not getting copied while copying the functiona module. Is there is any way which can help me to resolve this...
I am ware that it is not the ebst practice to copy but i have a small modification hence i was interested in copying rather then creating new,
thanks

IDOC : ORDRSP, Fucntion Module

Similar Messages

Maybe you are looking for