Inbound IDOC extension

Hi,
iam working on an inbound IDOC TPSSHT01, i need to add an extrta field and segment , so i create an data element and  Z segment and add the field in the segment
i have to copy the TPSSHT01 to a ZTPSSHT01 and do the IDoc extension ,
i have to copy the function module IDOC_INPUT_SHIPPL to Z_IDOC_INPUT_SHIPPL
Can any body let me know what are the steps that i have to follow to process the inbound idoc with the above requirment
Cheers,
Sai

Hi ,
      Follow this procedure .
In bound Idoc…
Step 1: Create segment
a.     T.code WE31
b.     Enter a new segment type and press create button
c.     Give a short text
d.     Enter the field names say FIELD NAME : MATNR ;; DATA ELEMENT: CHAR(18)
e.     Save the segment   (zkrishseg)
Step 2: Create IDOC type
a.     T.code WE30
b.     Enter a new IDOC type name
c.     Choose the basic type and press the create button.
d.     Choose the create new option button and enter a description and press enter
e.     Place the cursor on the type name and then press create button.
f.     Enter the segment name created in step 1 and check the mandatory segment check box
g.     Enter minimum number and maximum number as 1 and press enter.
h.     Then save the IDOC type.   (zkrishtyp)
Step 3: Create message type
a.     T.code WE81
b.     Press change button.
c.     Press new entries button.
d.     Enter a message type and short text and press save button. (zkrishmsg)
Step 4: Assign message type to IDOC type.
a.     T.code WE82
b.     Press change button
c.     Press new entries button.
d.     Enter the created message type, IDOC type and version release (46B or 46C)
Step 5:  Create a function module for inbound. (Z_IDOC_KRISH_INBOUND)
Step 5A: Create characteristics of inbound FM.
a.     T.code BD51
b.     Click ‘New entries’
c.     Enter the IDOC function module name and 1(individual type) in ‘input t.’.
d.     Save it.
Step 6: Assignment of FM to log, message and type.
a.     T.code WE57
b.     Go for change mode and click ‘new entries’.
c.     In processing by…enter FM name and enter ‘F’ as type.
d.     Enter basic type (idoc type-zkrishtyp) and message type (zkrishmsg) in the respective text boxes.
e.     Choose the direction as 2 – Inbound.
f.     Save the data.
Step 7. : Creation of inbound process code.
a.     T.code WE42
b.     Go to change mode and click ‘create entries’.
c.     Enter a new process code and description (zidockrish)
d.     Enter the FM name in the identification text box
e.     Choose processing with ALE service
f.     Choose processing by FM and click Save button
g.     In the next screen, select the FM name and click save button
Step 7a : Creation of inbound process code.
h.     T.code SM59
i.     Select ‘R/3 connection’  and click ‘create’.
j.     Enter all system related things(for Eg. Connection type as ‘3’, Target host as ‘SAP04’,
Description , and Logon  details and save.
Step 8:  Define a port
a.     T.code WE21
b.     Click on Transactional RFC and press the ‘Create’ button
c.     Enter a port name and description. (ztestkrish)
d.     Choose the release type.
e.     Choose the RFC destination.
f.     To create RFC destination…go to SPRO and search RFC destination…and create.
g.     Save the data.
Step 9. Define logical system
a.     T.code SALE
b.     Click down the sending and receiving systems
c.     Click down the logical systems
d.     Choose Define logical system.
e.     Go for new entries.
f.     Enter a new name and description and save it. (zkrishlog)
Step 10. Create partner profile
a.     T.code  WE20
b.     Choose partner type LS and click create.
c.     Enter the logical system name in partner number
d.     Then Save …. Here Type is ‘US’.
e.     click + icon(create inbound parameter) in the bottom. Note: Two table control subscreens will appear.  One for inbound and the other for outbound.  Click + icon in inbound area.
f.     Enter the message type, process code and save the data.
Step 11. Checking the Idoc
a.     T.code WE19,
b.     Choose radio Basic type , enter the type name(zkrishtyp) and press execute button.
c.     Click on EDIDC Number.
d.     Enter partner Number, Partner type, Port Number for sender and recipient ( data remains same here for sender and recipient)
e.     Enter Message type and press ENTER.
f.     Click on empty space corresponding to SEGMENT name and enter Paarameters like MATNR, WERKS and CHARG etc….
g.     Click standard inbound properties here…  and press enter… see the result….
h.     T.code WE02
i.     Enter IDOC number press ENTER see the status.
Function Module in Inbound
     Import Parameters
     INPUT_METHOD           LIKE BDWFAP_PAR-INPU              Inbound method for the IDoc inb 
MASS_PROCESSING     LIKE BDWFAP_PAR-MASS            Flag: Mass processing 
Export Parameters        
WORKFLOW_RESULT     LIKE      BDWF_PARAM-RESULT          Final value of method          
APPLICATION_VARIABLELIKE      BDWF_PARAM-APPL_VAR  Variable to be used by 
IN_UPDATE_TASK      LIKE      BDWFAP_PAR-UPDATETASK       Flag: Application has 
CALL_TRANSACTION_DONLIKE      BDWFAP_PAR-CALLTRANS        Flag: Application 
tables
     IDOC_CONTRL         LIKE      EDIDC                       Control record (IDoc)       
IDOC_DATA              LIKE      EDIDD                       Data record (IDoc)          
IDOC_STATUS          LIKE      BDIDOCSTAT           ALE IDoc status (subset of al
RETURN_VARIABLES    LIKE      BDWFRETVAR    Assignment of IDoc or documen
SERIALIZATION_INFO  LIKE      BDI_SER                Serialization objects for one
     Source code
FUNCTION ZASHOKMODULE.
""Local interface:
*"  IMPORTING
*"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
*"  EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE  BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE  BDWF_PARAM-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
data: begin of w_data occurs 0.
       include structure edidd.
data: end of w_data.
data: wa_data like ZASH1.
data : i_data like standard table of wa_data initial size 0.
*tables : zhemal1.
data : begin of wa_zhemal1.
        include structure zhemal1.
data : end of wa_zhemal1.
data : i_ZHEMal1 like standard table of wa_ZHEMal1 initial size  0.
read table idoc_data with key SEGNAM = 'ZASH1'.
loop at  IDOC_DATA into  W_DATA where segnam = 'ZASH1'.
  WA_DATA = W_DATA-SDATA.
  wa_data  = w_data-sdata.
  append wa_data to i_data.
endloop.
MOVE IDOC_DATA-DOCNUM TO IDOC_STATUS-DOCNUM.
    IDOC_STATUS-MSGID = 'ZABC'.
    IDOC_STATUS-STATUS = 53.
    IDOC_STATUS-MSGTY = 'S'.
    IDOC_STATUS-MSGNO = '001'.
    APPEND IDOC_STATUS.
LOOP AT i_data into wa_data.
wa_ZHEMal1-VBELN = wa_data-VBELN.
wa_ZHEMal1-POSNR = wa_data-POSNR.
wa_ZHEMal1-MATNR = wa_data-MATNR.
wa_ZHEMal1-MATWA = wa_data-MATWA.
wa_ZHEMal1-MATKL = wa_data-MATKL.
append wa_ZHEMal1 to i_ZHEMal1.
insert ZHEMal1 from table  i_ZHEMal1 accepting duplicate keys .
ENDLOOP.
ENDFUNCTION.
For Out bond  Steps are
1.     Create segment
2.     Create Type
3.     Create Message Type
4.     Assign message Type to Idoc Type.
5.     Create Port
6.     Define Logical systems.
7.     Define Partner profile.
8.     Create a Report program.
Report program Out bond
REPORT ZASH1 .
              Outbound standalone idoc creation                      *
Program Name : Y_VENMAST_OUTBOUND_STANDALONE                         *
Description  : Outbound standalone idoc creation for training        *
               to Unilever offshore team members                     *
Created by   : Satyam Computer Services Ltd.                         *
Created on   : 04.01.2002                                            *
                       Modification Log                              *
Developer           Date            Transport #   Details            *
Subramony         04.01.2002                                         *
Tables Declaration                                                   *
TABLES : zhemal1.
Internal table declaration                                           *
data : i_zhem1 Like standard table of zhem1 with header line.
data : control_record_out like edidc.
*data: p type p decimals 2,
     c(10) type c.
start-of-selection.
    p = '3.14'.
    c = p.
    overlay c with '0000000000000'.
  write c.
DATA : BEGIN OF I_EDIDD OCCURS 0.
        INCLUDE STRUCTURE EDIDD.
DATA : END OF I_EDIDD.
DATA : BEGIN OF I_EDIDC OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA : END OF I_EDIDC.
DATA : BEGIN OF I_zhemal1 OCCURS 0,
            VBELN LIKE zhemal1-VBELN,
            POSNR LIKE zhemal1-POSNR,
            MATNR LIKE zhemal1-MATNR,
            MATWA LIKE zhemal1-MATWA,
            MATKL LIKE zhemal1-MATKL,
       END OF I_zhemal1.
SELECT-OPTIONS : S_vbeln FOR zhemal1-vbeln .
START-OF-SELECTION.
  PERFORM F_GET_zhemal1.
END-OF-SELECTION.
Building Control record
CONTROL_RECORD_OUT-MESTYP = 'ZASH1'.
CONTROL_RECORD_OUT-IDOCTP = 'ZASH1'.
CONTROL_RECORD_OUT-RCVPRT = 'LS'.
CONTROL_RECORD_OUT-RCVPRN = 'ZASH1'.
CONTROL_RECORD_OUT-sndPRT = 'LS'.
CONTROL_RECORD_OUT-sndPRN = 'ZASH1'.
PERFORM F_PROCESS_OUTPUT.
*PERFORM F_FILL_EDIDD.
PERFORM F_CREATE_IDOC.
Form  F_GET_Y1COTU110                                                *
FORM F_GET_zhemal1.
  SELECT VBELN  POSNR MATNR MATWA MATKL
         FROM ZHEMAL1
         INTO TABLE I_ZHEMAL1
         WHERE VBELN IN S_VBELN.
ENDFORM.                    " F_GET_zhemal1
Form f_process_output                                                *
FORM F_PROCESS_OUTPUT.
  LOOP AT I_zhemal1.
  I_zhem1-VBELN = I_zhemal1-VBELN.
  I_zhem1-POSNR = I_zhemal1-POSNR.
  I_zhem1-MATNR = I_zhemal1-MATNR.
  I_zhem1-MATWA = I_zhemal1-MATWA.
  I_zhem1-MATKL = I_zhemal1-MATKL.
  i_edidd-segnam = 'ZASH1'.
    i_edidd-sdata  = I_zhem1.
    append i_edidd.
    clear i_edidd.
  ENDLOOP.
ENDFORM.                    " f_process_output
Form  f_create_edidc                                                 *
FORM F_CREATE_IDOC.
  CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            MASTER_IDOC_CONTROL            = CONTROL_RECORD_OUT
       TABLES
            COMMUNICATION_IDOC_CONTROL     = I_EDIDC
            MASTER_IDOC_DATA               = I_EDIDD
       EXCEPTIONS
            ERROR_IN_IDOC_CONTROL          = 1
            ERROR_WRITING_IDOC_STATUS      = 2
            ERROR_IN_IDOC_DATA             = 3
            SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
            OTHERS                         = 5.
  IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ELSE.
    LOOP AT I_EDIDC.
      WRITE :/ 'IDoc Generated  :' , I_EDIDC-DOCNUM.
    ENDLOOP.
    COMMIT WORK.
  ENDIF.
ENDFORM.                               " f_create_idoc
Please reward if useful.

Similar Messages

  • Inbound idoc MATMAS - find userexit to map extension

    Hi !
    I have an inbound IDOC MATMAS04 with a specific extension. I need to map the fields of the extension : some of them into an append of MARA, some others into characteristics.
    <b>I can't find the user exits I need.</b>
    I guess there are 2 of them. The first one for mara append BEFORE the creation of the material, and the second one for the characteristics AFTER the creation of the material.
    Does anyone know where I can find such user exits (even HOW to find them would be so much appreciated) ?
    Kind regards,
    Yann

    Hi..
    This is the Enhancement <b>MGV00001</b>
    and The FM exit is <b>EXIT_SAPLMV02_002</b> To Enhance IDOC for MARA segment in Inbound.
    <b>Reward if Helpful</b>

  • Creation of Sales Order and Service Contract from Inbound IDOC

    Hi Experts,
    My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
    I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
    Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
    I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
    Thanks in Advance.
    Regards,
    Priyabrata

    Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
    Regards,
    Priyabrata

  • How to create the INBOUND Function Module for INBOUND IDOCs

    Hi Friends,
    Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
    which are recieved from XI Server ?
    I am working in SAP-ISU
    Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
    We have a Standard INBOUND FUNCTION MODULE
    IDOC_INPUT_ISU_MR_UPLOAD
    which Uploads the Meter Reading Results.
    I copied the Same function Module into ZIDOC_INPUT_
    and working on it.
    Can any one suggest me, whether i am going in correct way or not.
    In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
    BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
    My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
    Can I Use the Same BAPI
    BAPI_MTRREADDOC_UPLOAD
    to Update the below fields,
    EABL-SERNR
    EABL-ZWNUMMER
    EABLG-ABLESGR
    EABL-V_ZWSTAND
    EABL-N_ZWSTAND
    EABL-ABLHINW
    EABL-ZSKIPC
    EABL-ADAT
    EABL-ATIMTATS
    EABL-ADATTATS
    EABL-ATIM
    EABL-ZMESSAGE
    EABL-ABLESER(Meter reader number)
    Kindly Suggest me,
    Thanks in Advance,
    Ganesh

    Hello Ganesh
    I think you are going completely astray with you z-function module for IDoc processing.
    If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
    EABL-SERNR => BAPIEABLU-SERIALNO
    EABL-ZWNUMMER =>REGISTER
    EABLG-ABLESGR
    EABL-V_ZWSTAND
    EABL-N_ZWSTAND
    EABL-ABLHINW
    EABL-ZSKIPC
    EABL-ADAT
    EABL-ATIMTATS => ACTUALMRTIME
    EABL-ADATTATS => ACTUALMRDATE
    EABL-ATIM
    EABL-ZMESSAGE
    EABL-ABLESER(Meter reader number)
    Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
    Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
    - BAPI_TE_EABL
    - BAPI_TE_EOSB
    Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
    Regards
      Uwe

  • Post long text for document line item via FI-GL Inbound IDoc

    Hi guru,
    I am trying post extension ZFIDCP02 linked basic type FIDCCP02 and message type FIDCC2 IDoc in R/3 (4.6c) via IBM Websphere (Inbound IDoc),
    I am use inbound function module IDOC_INPUT_FIDCC2 and activate exit 008 (EXIT_SAPLF050_008) and exit 002 (EXIT_SAPLF050_002),
    In the extension ZFIDCP02 and under E1FISEG, I am add my segment  ZITEXT include field TDSPRAS, TDID, TDOBJECT, TDLINE.
    I am send  ZFIDCP02 IDoc via IBM Websphere no error  but all field TDSPRAS, TDID, TDOBJECT, TDLINE in my segment  ZITEXT not post in FI-GL.
    How can I  post long text for document line item (ZITEXT) in FI-GL ?.
    and I'm mean post ZITEXT to bank statement via IDOC.
    Please throw light on this  and  may be I  'm want solution or example ABAP code for exit 002 (EXIT_SAPLF050_002).
    Thanks in advance,
    Akkapong Pirachai
    CAT Telecom
    Edited by: Akkapong Pirachai on Aug 20, 2008 7:40 AM

    Close question because long time for answer.

  • Problem with Inbound Idoc

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

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

  • Inbound idoc type

    i have to do an inbound idoc. first i need to retrieve data from one function module and use the data of that FM into another function module.
    so there is a Z function module which has information of both the function module.
    i am using the following idoc type
    MBGMCR02.
    i need to add some more zsegment into it of the other function module the function moduke is  WS_DELIVERY_UPDATE 2.
    kindly guide please.

    Hi Kamlesh,
    In we30 you have to create a new Extension idoc type and add the segments. and then from the menu release the idoc type.
    Create a new message type ZMBGMCR using we81 or we82.
    Create a new Function module to cater to your requirement.
    Create a new inbound Process code through WE42 or we41 and attach this function module to the process code.
    Link the idoc type, message type and function module through WE57 or BD57
    Set the partner profile We20 for the new message type and idoc type and also set the message control tab
    Set the port through we20. and give this port in the we21 partner profile.
    Create a Customer distribution model BD64 and give the sendor and receiver and from the menu distribute the partner profiles.
    Use We19 tcode to test the inbound idoc.
    Use we02 or we05 to view the status of the idoc.
    The tables for idoc are
    EDIDC - control record
    EDID4 - Data record
    EDIDS - Status record
    Some transactions are
    SCC4
    We20
    We21
    BD64
    we81
    we82
    bd87
    we19
    wedi
    we02
    Hope this helps
    Regards
    Arun

  • Regarding IDOC Extension

    Hi Experts,
    I need to Extend IDOC <b>COND_A03</b> with 5 Custom feilds. This Idoc will be populating 10 tables like A932,A933,A34,A35,A36,A37....,.I need to extend in
    <b>IDOC_INPUT_COND_A</b> through exit CALL CUSTOMER FUNCTION '002'.
    Here the 3 feilds will be present in A932 table and there will be only 4 feilds in A933 table and 3 feilds will be present in A934 table and so on. I..e all the 5 custom  feilds will not be present in all the tables.
    How i need to build the logic so that when the data comes to that function module i need to populate only 3 feilds into A932 table and 4 feilds into A933 table and so on..
    How do i need to build the logic.., to post the data when the number  of fields differ from one table to the other.

    ALE FUNCTION MODULE ENHANCEMENTS
    Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
    The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
    • For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
    • From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
    • Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
    Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
    All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
    When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
    • Execute transaction CMOD.
    • Enter name of project, say CSTMAST1.
    • Click on Create.
    • Enter a description of the project.
    • Save.
    • Click on SAP Enhancements.
    • Enter VSV00001 for Enhancement.
    • Save.
    Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
    As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
    The two important factors to consider while developing the customer function are:
    1. The point in the ALE function module where the function exit occurs
    2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
    Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
    Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
    Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
    Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
    • From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
    • Find Customer Function 001.
    • Double-click on 001.
    • The function EXIT_SAPLVV01_001 will be displayed.
    • Double-click on INCLUDE ZXVSVU01.
    • You will be asked to create a new include object. Proceed as desired.
    • Enter code (as in Listing 1).
    • Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
    Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
    To maintain the contact personâs business address of a customer:
    • Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
    • Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
    With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
    Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
    The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
    Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
    regards,
    srinivas
    *reward for useful answers*</b>

  • Custom inbound Idoc error handling/ Workflow

    Dear Experts,
            I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
    Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
    I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
    Thanks for your time.
    -Amit.
    Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
    Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

    Vittal,
    1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
    2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
    Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
    So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

  • Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

    Hello,
    the above segment is missing in the inbound idoc - basic type pexr2002.
    I have checked in TC-we30 and its available there.
    but still the idoc is getting generated without this segment.
    can someone suggest.
    thanks
    Arun

    Hi All,
    I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
    I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002  and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
    We have done the following steps:
    - BTE 2441 is available on our release
    - house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
    - entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
    - code maintained in ZXF08U04
    The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
    Can you advise what we might be missing please?
    Thanks and regards
    Mike

  • Inbound idoc failure(vendor invoice not posted)

    Hi All,
    we have two SAP systems. SAP A and SAP B.
    SAP A is the vendor for SAP B system we have created a sales order/delivery/out bound invoice in SAP A system.The sales order has BOM material with main item and sub items. We have the same material master data and BOM master data in system A and system B since we are following split architecture.
    The outbound invoice(with main and sub item) in system A has generated an outbound idoc and the idoc has gone to SAP
    system B. There are the usual segments like E1EDP01 for main item and another E1EDp01 for the sub itmes in the outbound
    idoc.The message type is INVOIC and basic type INVOIC02 with no extension.
    In system B, the inbound idoc (coming from system A) has failed giving the error message "higher level items not allowed". The
    segment E1EDP01 for sub item is highlighted in red ! basically the inbound idoc in sap system B is posting a vendor
    invoice since the inbound idoc in B is calling the FM IDOC_INPUT_INVOIC_MRM... I think this is doing vendor invoice
    verification.
    I have checked in system A, all is ok and the outbound idoc is ok but the issue is in sap system B, the inbound idoc has failed
    with message "higher level items not allowed". The segment E1EDP01 for sub item is highlighted in red in inbound idoc in
    system B. The segments are the same for inbound idoc in B and outbound idoc in A.
    Can someone pls tell what is wrong in system B.(config or data issue) as we are managing both systems.
    regds

    Hi,
    I am not sure if we can send both main  and sub items thorugh inbound invocie idoc to create vendor invoice.
    you can try to post the idoc by removing main items from the IDoc in WE19.
    one more thing you should aware is you are not allowed to to create two E1EDP01 segements for the same PO item(E1EDP02).
    check this as well.
    Regds,

  • Debugging inbound idoc user exit

    Hi all,
    I have a client who wishes to do some data validation when creating an inbound idoc.  We've identified the appropriate user exit and set a break-point in it, but how do I get the inbound process to stop here so I can see the data coming through, particularly since the process is initiated from a source external to R/3.
    The file data is coming from a warehouse management system into XI, and then being passed from XI through to the function IDOC_INPUT_DELVRY.
    Cheers,
    Stephen

    go thru the below information.
    IDOCs:
    - IDOC is an Intermediate Document'. It is simply a data container used to exchange information
    between any two processes that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
    -When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.
    This number is unique with in the client.
    - IDOCs are independent of the sending and receiving systems.
    - IDOCs are independent of the direction of data exchange.
    - In the IDOCs, data is stored in text format.
    - IDOC will wait until the Remote System is Active.
    *IDOC Definition Components
    - Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and
    any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has
    an attribute that defines whether the segment is option or mandatory.
    Minimum/Maximum range for each segment: It defines the maximum and minimum
    number of timesa data record corresponding to a segment cn exist in an IDOC.
    - Segments : A segment defines the format and structure of a data record.
    Segments are reusable componets. A segment consists of various fields that represent data
    in data record.
    IDOC Run time components:
    - A unique IDOC number 16 digits is allocated.
    - One control record is attached to the IDOC.
    - Segments translate into data records.
    - Status records are attached.
    - Sytax rules are checked.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC,
    this information basically includes the IDOC number, sender and receiver information,
    and information such as the message type it represents and the IDOC type.
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40.
    - The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number,
    hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as
    the IDOC achieves different milestones or encounters an error. At every milestone a statu code,
    date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for
    inbound processes.
    Message Type: Identifies what type of information transformed between logical systems or partners.
    Message type is not a local object type , it is transportable.
    Port : A Port defines the medium in which data is exchanged between the two systems in
    the ALE process, IDocs are transferred via memory.
    1. TRFC ports are used for ALE communicaion.
    2. File Ports used by EDI
    3. CPI-C ports used to communicate with R/2 systems.
    4. Internet ports used to connect with Internet Applications.
    5. ABAP-PI ports used to process data via the ABAP programming interface.
    6. XML ports used to process files in XML format.
    Partner Profiles:
    A partner profile has three views, which maintain different parameters for the partner.
    1. The General Parameters View : Values are stored in table EDPP1.
    2. The Outbound Parameters view : Values are stored in table EDP13, except for the
    Message control parameter , which are stored in table EDP12.
    3. The Inbound Parameters View: Values are stored in table EDP21.
    Transaction Codes :
    WE31- Segment Creation
    WE30 - IDOC structure
    WE81 - Message type creation
    WE82 - Link between Message type and IDOC type.
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    WE19 - Test tool for IDOC Processing.
    SALE - ALE (Application Linking and Enabling) settings
    Go through the link for basics related to IDOCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    You need to excahnge data between systems you need an interface as medium for data transfer.
    IDoc also treat one of the interface options for data transfer.
    Check this link
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    IDOC Debugging:
    1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).
    2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.
    For outbound function module debugging you can use the following:
    1) RBDMIDOC - for master IDocs configured via change pointers.
    2) RSNASTED - for transaction IDocs with output/message control.
    3) RSEOUT00 - For IDoc whose status is "to be processed".

  • Standar IDOC Extension

    Hello Group:
            I Need to Extend the Standard Idoc BUPA_INBOUND_MAIN_SAVE_M03.
            I created the New Segment with their fields in the WE31.
            Now, I want to Create the Extension in the WE30.
            But the Error is appearing:
            "Cannot create extension for generated IDoc types"
            Please, Anybody could tell me how correct it?
                                        Sincerely, Thank you, Herná

    Usually enhancement takes place when the content in IDocs provided by SAP are not sufficient for the business process. IDoc extension can take place whenever dictionary table has a new structure appended required by the business process.
    In brief IDoc extension takes place when extra fields are required for the business process.
    If you are creating a new IDOC.....
    1) Create segment (WE31)
    Of course it will have naming convention for different company. Here are some tips:
    2) Create IDOC Types (WE30)
    3) Create message type (WE81)
    4) Link message type with basic type (WE82)
    5) Create FM
    In the FM all the attributes should be the same for Inbound or Outbound. Basically you can get an example from the std FM
    6) Create Process Code (Inbound - WE41/ Outbound - WE42)
    7) Link FM with Basic Type

  • Inbound iDoc for POS message WPUUMS problem

    Hello all,
    I encountered a strange thing with the inbound idoc for POS with the message WPUUMS.
    I've created a new segment with we30 as an extension to the WPUUMS01 like this.
    WPUUMS01
    --E1WPU01
    E1WPU02
    ZNRLOT "this is my added segment
    E1WPU03
    E1WPU04
    E1WPU05
    E1WXX01
    The idocs (external xml files) enter correctly in SAP, when I view them with WE02 al the segments are correctly populated with the right data and they are ready for processing with status 64.
    After processing (with the program RBDAPP01 or with WE19 etc. doesn't matter, both uses IDOC_INPUT_POS_SALES_ACCOUNT ) comes the problem:
    The Material Document and Billing Document (Invoice) ARE GENERATED WITH ONLY THE FIRST ITEM. I mean that the iDoc has more items(materials) and should generate the material document and billing document with all the items, not just with the first one.
    As a conclusion:
    1. iDoc is loaded correctly in SAP with all the data in the segments, also in the new segment, and of course has more items.
    2. the problem is that after after processing, the generated document material and billing document have only 1 position, the first item from the iDoc.
    Any help in fixing this issue will be welcomed.
    Traian Mustata
    SAP ABAP Consultant

    check for the qualifier QUALARTNR. Is it filled accordingly in the z segment? U may also check by debugin the f/n module in we19

  • Creation of Service Contract from Inbound IDOC

    Hi Experts,
    I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a  Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
    So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
    Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
    Thanks in Advance.
    Regards,
    Priyabrata.

    Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
    Regards,
    Priyabrata

Maybe you are looking for

  • Can't open old files in Pages. Don't want to upgrade. Help please

    I am happy with my old Pages program ... some files I created on the old Pages open fine, as normal. However, some files I created on the old Pages (created in Dec. 2013) will not open. I get a pop up from Apple saying that I have to upgrade. I would

  • LASER JET 2840

    When you spend $1,000 for a desk top all in one printer you expect to use it for more than a year - especially when you purchased the printer after your previous HP all in one has died - you expect to be able to get HP drums & toner cartridges for yo

  • DVD Camcorder, anyone sucessfully able to import into to IDVD, I

    purchased the Panasonic VDR D220 and while an excellent camera in everything a camera should do it would not let me drag and drop to IDVD. Panasonic tech told me I needed "video arranger" but she had no idea where it was or even if it was a download.

  • Automate Checkout Process

    Hi, Oracle WCC:11g Oracle DB :11g Scenario: I have 50 Assets(Doc's, PDF .. soon) in my Content server. I want to do automate checkout for some assets say 20 and update content info of those doc's to revision 2 in content information page of WCC. (Thi

  • Precalculated web templates,Its scheduling time&Routines built on Queries??

    Hi ALL, <b>In the same way, I want the way to find out the list of Precalculated web templates, its scheduling time & Routines built on the Queries using RSRT T-code. Can anyone let me know to find out the Query properties using RSRT if we dont have