IDoc type ORDERS02

Hi friends,
I have a requirement here.
I am working with EDI Sales Orders.EDI Sales Orders will be coming in the form of IDOCs.
For each Sales Order Item,I need to check the pricing conditions.
In the <b>IDOC type ORDERS02</b>,
I am accessing <b>Item Number</b> from <b>E1EDP01-POSEX</b>.
To check <b>pricing conditions</b>,I am checking Segment <b>E1EDP05</b>.
Here <b>KSCHL</b> is <b>pricing condition type</b>.
Now,I need to check Condition value.I dont know which field it is ?
Regards,
Imran.

Hi,
I too thought KOBTR may be the one......
But,is it the same Condition value that refers to a Condition type as in VA01
TCODE ?
I need to compare the Condition values between two Condition Types.
To remind you,I am doing for EDI generated Sales Orders.
Regards,
Imran.

Similar Messages

  • Message Types in an IDOC Type

    How I can identify the various message types that are been plugged in an IDOC Type? What will be the Transaction Used to identify that?  I used the Transaction WE30, but I see the various segments that are been attached to the IDOC type and Not at the Message Type level. I used the IDOC type ORDERS02.
    SAP uses a single IDOC type for several logically related messages. For example, the Orders IDOC type (ORDERS02) is used for several messages, such as Order (ORDERS), Order Response (ORDRSP), and Order Change (ORDCHG).
    Create Message Type                          WE81
    Create IDOC Type                                WE30
    Assign Message Type to IDOC Type      WE82
    Can some one please help me? Appreciated.
    ,J

    You can check this in the table EDIMSG.
    Alternatively you can check this in WE82 as well:
    WE82 --> Menu func. 'Selection' --> By Contents --> Select "By Contents" --> I/P your basic type &  select "choose"
    This will give you the list of the basic types associated with the message types.
    Edited by: Suhas Saha on Jun 23, 2010 6:40 PM

  • Idocs, idoc types, tables

    can  anybody  tell me   what  type  of  idoc  types  are  typically  used  in  a regular  order to cash  cycle  in sd .
    and   are there   tables  related  to it?
      what is the tcode  to see  them
    n.bhardwaj
    my  id  is
    [email protected]

    Dear Neha,
    Idoc Types:
    ORDERS01     Purchasing/Sales
    ORDERS02     Purchasing/Sales
    ORDERS03     Purchasing/Sales
    ORDERS04     Purchasing/Sales
    ORDERS05     Purchasing/Sales
    INVCON01     Stock change data for inventory controlling
    INVCON02     Stock Change Data for Inventory Controlling
    INVOIC01     Invoice/Billing document
    INVOIC02     Invoice/Billing document
    INV_ID01     Invoice
    DELFOR01     Delivery schedule/JIT schedule
    DELFOR02     Delivery Schedule/JIT Schedule
    DELIVERYPROCESSING_EXECUTE01     Delivery processing
    DELVRY01     Delivery interface
    DELVRY02     Delivery interface with dangerous goods data
    DELVRY03     Delivery interface
    DELVRY04     Delivery interface
    You can view Idoc types in transaction WE30.
    WE02/WE05 for displaying IDOCs.
    WE19 for testing IDOCs.
    ALE and IDOC:
    ALE stands for Application Link Enabling and is used for distribution of data. IDOC is an Intermediate Document. It carries the application data from one server to another server.It uses the RFC(Remote Function call) .
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    It is the the combination of Segements.
    Segment : All the required fields will get assigned in relavant segement.Like that we will have lot of segments.We will assign all the segments to IDOC type.In the required level(Parent & child level .Like tree nodes).
    Idocs Type is a Structure by lot of segments.
    IDOC is generared at the time of run time .
    It will have the data.
    There are basically two types of IDOCs.
    Basic IDOCs : Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs : Extending the functionality by adding more segments to existing Basic IDOCs.
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sappoint.com/abap.html
    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
    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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    Need info on automatic determination of tax code at PO
    Hope this will help.
    Regards,
    Naveen.

  • Create Idoc Type under ECC6

    Hi folks,
    I've created a new Idoc segment for an existing idoc (The original idoc doesn't have the fields I need).  I'm now trying to create a new Idoc type taking into consideration the new Idoc Extension I've created.  When I type my new idoc type and select 'basic type', I believe I should get prompted (somewhere) to enter the Basic Idoc type and Extension type, but when I create a new basic type, I don't get the option to add my new extension.  And If I copy the original basic type, I don't get my new segments.
    Can someone please tell me what I'm missing in the create new Idoc Process?
    Cheers,
    Steve

    Hi Stephen..
    According to ur Scenario (Adding  new Segments to a Basic type ) , you should not create  a Basic idoc type . Rather you should create an Extended idoc type in WE30.
    That will ask for the Basic type and the new segments can be added here.
    This is the Complete info:
    1.     
    IDOC Enhancement
    This is the Complete Steps and Info on this...with an Example...
    Enhancing ALE
    For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
    let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
    IDOC EXTENSIONS
    Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
    Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
    In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
    In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
    1. Create an Extension Type and a New Segment.
    Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
    To create an extension type and new segment:
    • Use transaction WE30 or from WEDI go to Development -> IDOC types.
    • Enter ZDEBMASX for Object Name.
    • Choose Extension Type.
    • Click on Create.
    • You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
    • You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
    • You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
    • For 4.x, press Create after placing the cursor on segment E1KNVKM.
    • You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
    • Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
    • Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
    • For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
    • Click on Segment Editor.
    • On the next screen, click on Create.
    • Enter a development class for the object. Enter.
    • This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
    • Enter these three columns for all 12 fields. Save.
    • Click on Generate/Activate, F3 to step back.
    • From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
    • Save again to store the descriptions of the segment, F3 to step back.
    • Save the extension type.
    It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
    2. Create an IDOC Type.
    The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
    • From transaction WE30 or WEDI go to Development -> IDOC Types.
    • Enter ZDEBMASZ for Object Name.
    • Click on IDOC Type.
    • Click on Create.
    • Enter DEBMAS02 for Basic IDOC type.
    • Enter ZDEBMASX for extension type.
    • Enter a description.
    • Enter.
    • You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
    It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
    3. Link IDOC Type to Message Type.
    The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
    • Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
    • Click on Display <-> Change.
    • Click on New Entries.
    • Enter DEBMAS for message type.
    • Enter DEBMAS02 for Basic IDOC type.
    • Enter ZDEBMASX for extension type.
    • Enter your SAP R/3 release number for Release.
    • Save.
    This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
    4. Check the IDOC Type.
    Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
    • From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
    • For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
    • The extension type has now been "released."
    You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
    • From transaction WE30 or WEDI go to Development -> IDOC types.
    • Enter ZDEBMASX for Object name.
    • Click on Extension Type.
    • From the Development Object menu select Check.
    • Repeat the operation for IDOC type ZDEBMASZ.
    • A check log will be generated for each run with details of correctness or errors (see Figure 4).
    In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
    Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
    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.
    Reward if Helpful.

  • Extension of generated Idocs types

    hello,
    does anybody knows why I can not create extension of generated (means in table EDBAS-GENERATED = 'X') idocs?
    I tried to extend idoc BATMAS03 on R/3 Ecc 6 and got message:
    message e099(b1) with
             'Action is not possible for generated idoctypes'
    In former version of R/3 4.6C it was possible to extend such IDoc BATMAS02 (generated one) without any problems.
    Of course I found in program MSED5F02  in routine CREATE_EXT_STRUCTURE new (in comparison to 4.6C) extra check which protects against extension of generated IDocs, but I want to get to know what was behind that decision or how to workaround that problem.
    Thanks in advance,
    Marcin

    Hi,
    User Exits are used to populate data in new segments added and to read them
    back which provides extension to existing idocs.
    IDOC EXTENSIONS
    SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type. Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
    In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
    In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
    1. Create an Extension Type and a New Segment.
    First, determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
    To create an extension type and new segment:
    Use transaction WE30 or from WEDI go to Development -> IDOC types.
    Enter ZDEBMASX for Object Name.
    Choose Extension Type.
    Click on Create.
    You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
    You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
    You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
    For 4.x, press Create after placing the cursor on segment E1KNVKM.
    You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
    Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
    Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
    For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
    Click on Segment Editor.
    On the next screen, click on Create.
    Enter a development class for the object. Enter.
    This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
    Enter these three columns for all 12 fields. Save.
    Click on Generate/Activate, F3 to step back.
    From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save. Save again to store the descriptions of the segment, F3 to step back.
    Save the extension type.
    It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
    Pls reward helpful points.
    Regards,
    Ameet

  • IDOC type to send OPEN ITEMS per INVOICE to external system?

    Dear EDI Experts,
    we want to send OPEN ITEMS of a customer per document via EDI to an XML file.
    We checked on idoc type CRESTA01 but this idoc type provides "only" the total OPEN ITEMS of a customer but NOT e.g the invoice document numbers.
    Is there any way to generate an IDOC or XML file with the invoice numbers and its OPEN ITEM amounts?
    We want to transfer that data to an HH device in order to show customer which invoices yet to be paid.
    Any idea?
    Many, many thanks
    Regards
    JW

    Hello,
    many thanks for the quick answer to my question.
    We want ONE credit idoc per one customer showing all OPEN ITEMS with the document number.
    That info is sent to the Handheld in order to provide customer exact info which invoice he has not paid yet.
    We do not need ONE idoc per ONE document.
    But it seems no standard idoc provides such info and we have to call a FM to provide that info to a Z-Segement of CRESTA01. Is that correct?
    Port definition XML in we21 for idoc type is understood.
    Thanks a lot
    Regards
    JW

  • PO and SO IDoc Type

    Hi,
    I understand that the IDoc type ORDERS05 can be used for Sales Order as well as Purchase Order. My requirement is to receive Order IDoc and create the sales order and send the PO details to a partner. Please let me know whether I can use the IDoc ORDERS05 for both these cases.
    Also I found that IDoc type PORDCR04 is available for PO. Can we use this IDoc type for sending Purchase order details.
    Thanks
    N

    Hello Nanditha,
    Yes you can do that.
    Also go to WE60 and put in PORDCR04 and downloadd to your PC if needed.
    Then search if all the fields you need are in that Idoc type.
    There are no rules as to which Idoc type you have to use, but you should try your best to stick to SAP recommended one's.
    Hope this helps.

  • How can I design a BPM with mulitiple IDOC types as sender

    Hi Experts,
      I am using PI 7.1
      I have a senario that I have to design a BPM in such a way that I will get different IDOC types as sender while the receive step has to trigger the the respective IDOC types at run time.
    For example: when matmas is the IDOC the BPM instance have to trigger only the respective Abstract interface at runtime.
    In my senario I have 5 IDOC TYPES which should pick the related one using a single Abstract Interface in the same design( one BPM ).
    Is this possible. Please suggest me how can I do this if possible.
    Regards
    Shankar.

    Hi,
    you could work with multiple receive steps that triggering the process.
    Similar to the example pattern in SAP Basis BpmPatternSerializeMultipleTrigger
    http://help.sap.com/saphelp_nw04/helpdata/en/77/0737133012b24b9d0a12c6df2b1054/frameset.htm
    In the fork step you could set the number of required branches to 1 that means only one receiving IDoc is required to leave the fork step.
    Regards
    Patrick

  • Error while creating an outbound idoc using idoc type delvry02

    hi,
         i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
    ERROR:
                " SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
    MESSAGE NO: AM053
    Help would be appreciated.
    regards
    leo

    The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
    It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
    Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

  • RSAR2318 : IDoc type for source system T90CLNT090 is not available

    Hi all,
    I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
    1. Error:
    R7I028
    Object could not be activated
    2. Error:
    RSAR238
    IDoc type for source system T90CLNT090 is not available
    Error when creating the export datasource and dependent objects
    Error RSAR238 : IDoc type for source system T90CLNT090 is not available
    I have already checked trx & dtps, but could not find resolution.
    Kindly help me with this error.
    Thanks and regards,
    MS

    M Sharma wrote:
    But how exactly can I create when T90CLNT is not active? Help please.
    Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

  • RSAR238 : IDoc type for source system T90CLNT090 is not available

    Hi all,
    I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
    1. Error:
    R7I028
    Object could not be activated
    2. Error:
    RSAR238
    IDoc type for source system T90CLNT090 is not available
    Error when creating the export datasource and dependent objects
    Kindly help me with this error.
    Thanks and regards,
    Dhanapal

    Hi,
    Check the same in SDN..
    Object ZDUMMY could not be activatedMessage no. R7I028
    Re: DSO Activation problem
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
    Thanks
    Reddy

  • IDoc type could not be determined for the IDoc

    I am trying to Post the payment run through the transaction F110.
    In the payment run log i get the following message:
    "IDoc type could not be determined for the IDoc"
    But in fact the IDoc is generated and it is displayed in We05.
    I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
    Has anybody Idea about why this error is coming and how i can resolve this?
    This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
    Would appreciate if anyone can please help on the same.
    Thanks & Regards,
    Narayanan

    Hi,
    If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
    still if you are having any problem
    Check in the below path:
    IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
    2. Assign Release Approval Procedure for Release for Payment
    3. Define Users with Authorization to Payment Release
    Thanks
    Chandra

  • IDoc type could not be determined for the IDoc in F110

    Dear All,
    The below mentioned error is encountered by us in F110.We have check all the setiing  and not able to find the solution for this error.
    Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
    The system is not creating the IDOC file.....
    IDoc type could not be determined for the IDoc
    Message no. B1090
    Diagnosis
    The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
    The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
    The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type  from field DOCTYP.
    Procedure
    Possible error sources:
    - The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
    - The IDoc type  is not known in your system and must be maintained.
    Kindly do the needful.
    Regards

    If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
    see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

  • How to find out the idoc type required for our requirement

    Hi,
         How to find out the list of available idoc type in SAP. It will be good if i get to know the table name where all the idoc type definitions are gets stored.
    Say i have some requirement and for that requirement how i can find the proper idoc type to be used. (assume functional consultant is not providing that information)
    Points will be given for the useful answers
    Thanks,
    Prasanna

    Hi prasanna,
                    we can get SAP idoc types in tcode we31.For every requirment there will be different message type.
    For example we want idoc type for account invoice receipt.
    First find out message type for that purpose which can be found in we81-ACC_INVOICE_RECEIPT.
    Get this message type and search in we82  where we can find message type and idoc type linkage.
    try this way.
    Reward if it is usful.
    Thanks,
    Srikanth.A

  • Idoc Type for Goods Receipt against a PO

    Hi ,
    The Goods Recept is already done in my legacy system, So my interface updates the goods receipt in SAP based on goods receipt done in Legacy system.
    I receive following data:
    Plant
    Purchase Order Number
    Line Item
    Pack List Number
    Material Number
    Quantity
    Storage Location
    GM_CODE = '01'
    MVT_IND Movement indicator = 'B'
    So I want which Standard Idoc Type I can use for this.
    I reffered to Note 833603.
    In that
    1. WMMBXY (WMMBID01, WMMBID02) and
    2. MBGMCR (MBGMCR01, MBGMCR02) is mentioned.
    Which one I should Use, as this GR is done again PO so its mandatory for me to pass Purchase Order Number and line item.
    Plz guide me which IDOC type i shd choose.

    Hi,
    Use the message type WMMBXY, IDOC Type as WMMBID02 and the function module is L_IDOC_INPUT_WMMBXY (Process Code WMMB) to process the Goods Receipt against a PO.
    I have successfully used that in many projects till now.
    Please let me know if you have any queries.
    Thansk,
    Mahesh.

Maybe you are looking for

  • Generate XSL from XSD ?

    Please let me know the steps involved . I need to generate XSL's from XSD's created in my application where am using IBM RSA 7.0 . After generating XSD am converting the same into XML but i could be wrong doing so as it shows errors in my xml file. M

  • Code to get the latest version of an entitiy using wcf?

    Hi, I am using WCF services to get entities in MDS. I want to get the entities only in the l;atest version. Can you please share code/api asto how to get the latest version of a model in MDS using WCF? Thanks

  • RFC Sender EOIO, is it possible?

    Hi ! We have a RFC-XI-FTP scenario. We need to build files in the FTP server using the contents received by the RFC sender from R/3. The problem is that we need to ensure that the files are rebuilt exactly on the FTP server side. We are NOT allowed t

  • Multiple file types in sUser- GetFileDialog() ?

    I'm using the GetFileDialog function of the AIUser suite. I'd like three options in the file type popup below the file list (Labeled "Enable:"), such as: All Recognized files types ("jpg", "jpeg", "gif") JPEG files ("jpg", "jpeg"") GIF filess ("gif")

  • Snow Leopard and MacBook Pros

    Hey, O.K. I've got a brand new unibody 17" MacBook Pro. It's loaded to the hilt, and I paid a fortune for it. Unfortunately, it's a **** good-looking paperweight. After only 51 re-cycles on the battery and several weeks of usage, I bought it in Augus