Extending basic type SDPIID01

Hi,
I have to extend basic type SDPIID01 and add custom segments, After adding those segments I need to update records in those custom fields that would get stored in the databse table using Idoc.Pls suggest the complete steps and the any enhancement or exits that I need to implement to update the values in the database.Also pls suggest the logic that needs to be written inside that enhancement, exit or BADI.
Thanks in advance
Anand

Hi go to we30
Give one zidoc type name and create with radio button extension.
Choose create newlinked basic type , give ur basic type  as SDPIID01
Then enter description and say ok.
and save .
Now Clk on the segment under which u want to add ur zsegment wether u want to add on hraedr level or item level.
and click on craete .
Enter a segment name , minimum1  maximum u can gv as per u like 10 , 99 etc.and ok.
It will take u to the segment structure , where u have to add the zfields.
For detail u can go through some documents or helps.
Regards

Similar Messages

  • EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

    Hi,
    I'm trying to various infotype 2001,2002,2006 ecc to another SAP system via ALE and since they are not part of message type "HRMD_A" I have created the extension ZHRMD_A06. I've already created the new segments(we31) and put these segments (with names Z1P2001, Z1P2002 ecc ecc) into the extension(we30). And I've assigned the extension to the message and basic type (we82).
    The new segment are processed correctly in the idoc creation via transaction PFAL, but via transaction BD21 i meet the abend message : B1 070 - Internal Error : program....command... for argument Z1P2001 (for example)
    In other words, BD21 do not process the custom segment but the PFAL yes...how it is possible?
    I've activate the change pointer in every customizing table intersting.
    Many thanks in advance for any reply
    Achille

    unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
    are between the structures i must send in the other system sap.
    Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
    Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
    all correct!!
    By checking Filters I mean that confirm if you have added Time Infotypes there (just
    making sure). If data is appearing in BDCP2 that means there is no problem in Change
    pointer creation, Just ruling out possibility.
    Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
    is created without problems and in the BD21 no??? This is very strange
    1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
    create IDOCs. So now if you have extended Segment you have to add your population code
    here somewhere.
    2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
    populate Additinal segments data here? Otherwise IDOC will not be populated
    automatically.
    Let me know what you think.

  • Extend BASIC Type HRMD_ABA (HRM Module) - Custom Extention

    Hi I have extended IDOC Message type HRMD_ABA to include custom Infortype. We are planning to use Change Pointer.
    How can BD21(generate idoc from change pointers) populate custom infotype data into the IDOC?
    Thanks,

    Hello KuPatel_PI ,
                                  Automatically nothing happens. You need the find an user exit to populate the data  for the custom info type related data to populate the IDOC custom segments that you had added.
    You need to locate an user exit inside the FM "RH_MASTERIDOC_CREATE_HRMD".
    you can try the below user exits that suits your requirement:
    EXIT_SAPLRHAL_003
    EXIT_SAPLRHAL_001
    EXIT_SAPLRHAL_004
    EXIT_SAPLRHAL_002
    Hope this answers your question.
    Thanks,
    Greetson

  • Unable to extend the basic type "SALESORDER_CREATEFROMDAT202"

    HI
    when iam trying to extend the IDOC basic type "SALESORDER_CREATEFROMDAT202" iam getting an error message "Action is not possiable for generated IDOC types"
    To my understanding SALESORDER_CREATEFROMDAT202 is a bapi.So, I guess we can not extend these type of IDOC directly.
    Can any one can help me how to copy the BAPI interface and extend it....
    or any other solution for this......
    can any one can help me reg this.....

    I will answer my question!
    This is the proble of version we are useing!
    the extenction is possiable in sap 4.6 version.
    but it is not possiable in ecc6.
    So follow the steps i have done
    created a new basic type "ZSALESORDER_CREATEFROMDAT202"
    where icopy the basic type "SALESORDER_CREATEFROMDAT202" to it
    Then i extened the IDOC "ZSALESORDER_CREATEFROMDAT202"
    and added the new segments.
    FInally while assiging the basic type to extended IDOC  given basic type as "SALESORDER_CREATEFROMDAT202"
    And assigned to the message type "SALESORDER_CREATEFROMDAT2"  to it
    then we can use this Structure with
    Message type: SALESORDER_CREATEFROMDAT2
    Basic type: SALESORDER_CREATEFROMDAT202
    Extended:SALESORDER_CREATEFROMDAT202EX
    for data picking u can code in the followin function modules:
    Function Module for Outbound ALE
       ALE_SALESORDER_CREATEFROMDAT2
    Function Module for Inbound ALE
       IDOC_INPUT_SALESORDER_CREATEFR
    There is another method also for this:
    create a bapi fm with all the requirements and go to swo1 tc create an object with method as BAPI FM created.then go to TC bdbg and create a bapi ale interface.this  will automatically generates the inbound and outbound FM's .Then the idoc will be generated with the added segments...

  • Prob wth Extending HRMD_A06 basic type

    Hi All,
    I have some custom fields in PA0002 table. So i extended HRMD_A06 and in user-exits i am populating custom fields. Out bound side everything is OK. But it is giving 51 error in inbound side. Probelm with read_namtb subroutine. it is chking the custom segment in T777D table...
    I am unable to solve the problem. Can anyone hlp me in this regard.

    May be this helps you !!
    <b>
    FYI</b>
    <b>Symptom</b>The standard scenario for the distribution of HR master data and organizational data via message type HRMD_A only covers a limited number of infotypes.
    Additional standard infotypes should be distributed using a customer enhancement.
    Other terms
    PFAL, RHALEINI, HRMD_A
    Reason and Prerequisites
    In the standard scenario, only infotypes are distributed, which are required for a distributed HR in a non HR-system.
    Solution
    The following activities are required if standard infotype Pnnnn (with nnnn = infotype number) is to be distributed in addition.
    Consider the restrictions at the end of this note in particular!
    Release 3.1
    1. Source code corrections:
    According to the attachment (programs not contained in the standard system), repairs are necessary in the Includes LRHA2U06 and UP50RU01.
    You only have to change Include UP50RU01 if it is a PA infotype.
    If you also want to distribute infotypes starting with 2nnn or 9nnn, an additional repair in Include LRHALF01 is necessary. Remember that in this case the Infotype 2011 is stored differently than the other infotypes and cannot therefore be distributed.
    Note that these changes are not contained in the standard system.
    2. Customizing:
    Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system):
    For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number).
    Transaction SM30 for table T777D only for PD infotypes (in the sending system and the receiving system):
    For the entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
    Transaction WE30 for ZRMD_A01 (in the sending system and the receiving system):
    With Transaction WE30, create extension ZRMD_A01.
    Create E1PITYP as a reference segment type, as child segments of this, the extension segment types Z1Pnnnn. As an IDoc type, create ZRMD_A01 for the basic IDoc type HRMD_A01 and extension ZRMD_A01.
    Transaction WE82 (in the sending system and the receiving system):
    The entry for message type HRMD_A and basic IDoc type HRMD_A01 is copied to a new entry with the extension ZRMD_A01.
    Transaction WE20 (in the sending system):
    In the sending system, for the partner number of the receiving system in the outbound parameters, enter ZRMD_A01 as idoc type in the line for entry message type HRMD_A.
    Transaction WE57 (in the receiving system):
    Copy the entry for function module name IDOC_INPUT_HRMD, basic IDoc type HRMD_A01 and message type HRMD_A, and enter ZRMD_A01 in the field extension.
    As of Release 4.0B
    1. Source code corrections:
    Implement the attached advance corrections or:
    Apply Hot Package for 4.0B:   SAPKH40B02 or
    Legal Change Patch for 4.0B:  SAPKE40B02
    The Include UP50RU01 must only be changed if it is a PA infotype.
    Include UP50RU01 is not contained in the Hot Package and must be changed in accordance with the advance correction if the Legal Change Patch is not applied.
    After applying the Hot Package (and manually repairing the UP50RU01) or the Legal Change Patch, only the Customizing activities are necessary.
    2. Customizing
    Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system) :
    For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number). The function "Create by copying" can be used to reduce the work load.
    Transaction SM30 for table T777D (in the sending system and the receiving system):
    For entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
    Transaction WE30 for ZRMD_A02 (in the sending system and the receiving system):
    With Transaction WE30, recreate extension ZRMD_A02.
    The linked basic type is HRMD_A02. Insert the new Z1Pnnnn segments as child segments of E1PITYP.
    Transaction WE82 (in the sending system and the receiving system):
    Copy the entry for message type HRMD_A and basic type HRMD_A02 to a new entry with extension type ZRMD_A02.
    Transaction WE20 (in the sending system):
    In the sending system enter ZRMD_A02 as an 'Extension' for the partner number of the receiving system in the outbound parameters in the entry message type HRMD_A with basic type HRMD_A02.
    Transaction WE57 (in the receiving system):
    Copy the entry for the FM name IDOC_INPUT_HRMD, basic type HRMD_A02 and message type HRMD_A, and in field 'Extension' enter ZRMD_A02.
    As of Release 4.5A
    Here, the Customizing activities described in Release 4.0B are to be carried out.
    As of Release 4.5A, HRMD_A03 is used as the basic type and ZRMD_A03 is used as the extension type.
    As of Release 4.6A, HRMD_A04 is used as a basic type and ZRMD_A04 is used as an extension type.
    As of Release 4.6C, HRMD_A05 is used as a basic type and ZRMD_A05 is used as an extension type.
    As of Release 4.70, HRMD_A06 is used as a basic type and ZRMD_A06 is used as an extension type.
    Restrictions:
    SAP cannot offer any support concerning compatibility with different releases for the additional infotypes of the enhancement in the standard system. For release specific changes to the infotypes of the enhancement a client-specific solution must be found (project solution).
    Other known restrictions:
    Known restrictions are listed here with possible solution approaches. If you should discover a restriction that is not yet documented, you can inform us of this via the R/3 SAPNet Frontend with a low priority problem message.
    01/25/1999: PA infotypes with subtypes are not found in T591A
    For infotypes in personnel administration, whose subtypes are stored in a different table than T591A according to table T582A, distribution works in the transfer mode 'Insert' and using the change pointers. Distribution in the transfer mode 'Update' does not work. The approach to solve the problem is a customer-specific extension of the routine HR_INFTY_GET in program RHALEINI by the corresponding infotype/subtype combinations.
    02/01/1999: Workflow infotypes
    Workflow infotypes, thus in the area 12xx, are not supported since the object type workflow is not supported in the standard ALE scenario. The approach to solve the problem is the use of the manual transport connection (RHMOVE30).
    05/17/1999: Infotype 2011
    The Infotype 2011 is stored differently than the other infotypes and therefore cannot be distributed.
    11/09/2000: Segment for infotypes with a width of more than 1000 characters
    The maximum width of a segment is 1000 characters. For this reason it cannot be generated automatically for infotypes with a width of more than 1000 characters.
    A possible solution is to create the segment manually and to only insert the key fields and the application fields that are really needed in the segment in order to avoid exceeding the 1000 characters. The values of the fields are transported from infotype into the segment and vice versa in the case of infotypes that are distributed additionally. The reason is that the fields have the same names in segment and infotype.
    07/17/2002: In ALE inbound processing, only the data records of the infotypes are posted - similar to the infotypes to be distributed in the standard. No additional functions regarding possibly dependent or derived data in other (database) tables are executed. A solution approach is to distribute the dependent or derived data in a separate (customer) scenario or implement a customer exit (RHALE001) or a BADI (HRALE00INBOUND_IDOC) with the desired functionality.
    <b></b>

  • Add IT0006 custom fields for segment definition E1P0006 basic type HRMD_A06

    Hello!  I am am trying to determine how to bring in our custom fields from IT0006 into our IDOC's for message type HRMD_A basic type HRMD_A06 without performing a custom SAP modification.  I was able to create a new segement definition called Z1P0006 and replace the SAP standard E1P0006 IDOC segment defintion in table T777D for infotyp 0006 to Z1P0006.  However, I receive a message that I must not maintain this IDOC segment manually and instead you must maintain infotypes and their individual elements by using the transactions for processing infotypes: PPCI or PM01 (Infotype copy transaction for personnel administration). 
    Does anyone know of a way to bring in the new custom infotype fields from i.e. reimport the table structure for IT0006 into the segment definition without a custom SAP modificaiton?  I would really appreciate any help on this topic!
    Thanks!
    Holly

    unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
    are between the structures i must send in the other system sap.
    Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
    Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
    all correct!!
    By checking Filters I mean that confirm if you have added Time Infotypes there (just
    making sure). If data is appearing in BDCP2 that means there is no problem in Change
    pointer creation, Just ruling out possibility.
    Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
    is created without problems and in the BD21 no??? This is very strange
    1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
    create IDOCs. So now if you have extended Segment you have to add your population code
    here somewhere.
    2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
    populate Additinal segments data here? Otherwise IDOC will not be populated
    automatically.
    Let me know what you think.

  • Basic type and idoc type

    hi iam having z-basic type how to find what is the standard idoc type(for ex MATMAS,Creamas) for that

    Step1. Go to WE30 and give the extended IDoc name
    Step2. Check the extension button and click on display
    Step3. Click on header button (Top 3rd left button)
    Step4. In Technical Attributes, you will get the name under "Linked Basic Type"
    Hope it solves your query...
    Regards,
    Prasoon Sahay
    Edited by: Prasoon Sahay on Sep 2, 2009 2:18 PM

  • IDOC basic type

    Hi guys,
    Is there anyway to find out the right Basic type which suites our requirement?
    Sahil

    Hi Michal,
    My requirement is whenever a material is created/changed an IDOC should be triggerd.
    we are using change pointers concept here.
    MASTERIDOC_CREATE_SMD_MATMAS is used to record the changes and its get triggerd when we create/change and then pass the idoc to PI for further processing.
    I am also extending my IDOC by adding few fields.
    My question is:
    1.How do i know which basic type to use?
    2.Do i need to populate the fields for an extended IDOC using some enhancements/EXITs or just pass the extended IDOC to PI?
    please reply
    Sahil

  • Extend idoc type WPUTAB01

    I have to extend a idoc type 'WPUTAB01' so i can include some fields that dont exist in the idoc.
    How i can do this?
    tks
    regards
    Luis

    Hello Luis,
    1. Goto Transaction WE31. Create new segment with additional custom fields.
    2. Goto transaction WE30. Put new Z extended idoc name and select Extension Radio Button.
    3. On next screen select second radio button (Create as Copy) and put 'WPUTAB01' infront of Linked with basic type text box.
    4. On next screen Click on "Create Sgement" and insert segment which you have created with custom fields.
    5. Goto Edit-> Set Release..
    thats it.
    Cheers,
    Nilesh

  • Basic Type determination

    Hi Gurus,
    I need to develop an outbound interface. It contains some Zfields and also the below mentioned standard fields from the given below tables.
    PA0002,PA0077,PA0050,PA0014,PA0000,PA0001,PA0041,PA0006.
    Could anyone kindly let me know what is the basic procedure to determine the basic type based on tables or infotypes.
    Thanks
    G Natasha.

    Dear Natasha,
    Firstly to select the basic type you will use, you need to choose the highest version in the two systems (for e.g. HRMD_A06) using transaction WE30. Then you need to extend this message type (create an extension). Please check out note 105148 : HR-CA-ALE: Additional infotypes for distribution. In this note, it will help you to create new segment according to your requirement.
    For e.g.  you have to create an extension using transaction WE30 with name for e.g. ZRMD_A06
    for IT0077, you will have to create a new segment type Z1P0077 and to update it table T777D only for PD objects.
    It is all explained in the note. Hope it helps,
    Christine

  • Extending Basic Idoc's

    Hi,
       Please provide Step by step procedure to extend Basic Idoc's.
    With Regards,
    Nelson

    Choose SAP Menu ® Tools ® Business Communications ® IDoc Basis ® Development ® IDoc types . The IDoc type editor is displayed.
    If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting  you can return to the IDoc type editor.
    Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
    The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
    Choose one of the following options:
    Create New: Create the extension without a reference.
    Create copy, which you can then change if necessary
    Create as successor: Note that only one successor is allowed per release for each extension.
    Select the basic type which is to be combined with your extension. Confirm your entries.
    The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
    Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
    Mandatory segment (indicator): Must data be written to this segment in the IDoc?
    Maximum and minimum frequency of use: How often may/must a segment occur in the IDoc?
    You can add further children or "grandchildren" to this or any other reference segment in the basic type.
    When the new extension is complete, you can save your entry.
    You should keep the following factors in mind when dealing with extensions:
    Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
    Parent segments of predecessors must remain parent segments in the case of successors.
    Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
    In the example call your extension Z1ORDERS . Append Z1TEST1 child segment to E1EDP19 reference segment in ORDERS01 basic type. The child segment can be used only once.

  • How to change the default IDOC basic type from CREMAS05 to CREMAS04.

    Hi All,
    How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
    When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
    I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
    Thanks
    Sai Krishna

    execute WE20 and edit the outbound parameters
    here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
    Edited by: Jürgen L. on Sep 7, 2011 9:49 PM

  • Error in idoc of basic type artmas05 - status 51 with Message no. MG537

    Hi all,
         I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
    *The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
    field; it does not contain an entry
    *The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry        
    *The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    *You have not fully maintained the tax classifications
    *The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
    It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
    Thanks in advance,
    Revathi.

    Hi,
    Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
    The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
    The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
    The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    Regards,
    Gowri.S

  • Reg : The functionality of WMMBID02 Basic type in SAP.

    Hi All,
    Can anyone give me the functionality of WMMBID02 Basic type in SAP. Mean, not the structure of the Idocs i am talking about. But to which Module of SAP is it related to and what kind of inventory data it carries? what the significance of this data. which table get updated when this idocs gets posted successfully.
    And also that, From table /GLB/RGTTPLANHED, we can get the trip status. So wat exactly this trip status indicates?... can anyone explain this in detail?

    The message typer for this is WMMBXY and its used for Goods movement between storage location. This would internally calls MB01 transaction and related to MM module.

  • How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)

    I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
    The requirement looks very simple but for this, as per my knowledge, I have to create a new  Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
    It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
    Can we do it any other way to handle this kind of situation?
    Thanks in advance for your suggestions and help.

    Hi Phani,
    You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi  to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
    3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
    4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
    Let me know if this helps.

Maybe you are looking for