Idoc type provided by ECC to hold all project data

Hi All,
Please provide me the Basic Idoc type and message type provided by ECC which hold all project data like WBS Elements Info, Network & Activity info.
Thanks,
Suresh

Hello,
Please check if Basic Type PROJECT01and Message Type PROJECT suits your requirement.
BR/Yogesh

Similar Messages

IDoc types supported by ECC 6

Hi Friends,
Could you please let me know what are all IDoc types are supported by ECC 6.0?
Any documents or link would be more helpful.
Regards,
Krish

Hi Krish,
Go to Tcode: WE30 and do a F4 on the Obj. Name field this will list all the IDOC Types supported by SAP, to get more information go to WE60(you could do a F4 here too - against Basic Type) and use the IDOC Type to read the documentation for the same.
Regards,
Chen
Edited by: Chen K V on Jun 15, 2011 10:51 AM

IDOC types in SAP ECC

Hi Gurus,
1) 3rd party->PI->SAPECC
We have a requirement that the tenant refunds coming from 3rd party system should be sent to SAP ECC system.
To send this messgae to SAP ECC, is there any separate idoc format for this tenant refunds.
Should I use any FICO or any other standard module to post these files to SAP ECC.
2)SAPECC->PI->3rd party
Also is there any IDOC type for the direct debit details and customer payments or should i run the F110 transaction to execute the customer payments and to send the paymnet files to PI.
Coould you please advise.
Thanks,
Jay.

If you have fair understanding about ECC then you can easily identify which IDoc to use or any extension required for existing IDoc.
otherwise better to talk with ABAP/Functional team they will help you.

How to update all projects data (checkout-edit-save&publish-checkin)?

Hi every one,
we have more that 400 projects in pwa and it will take too much time to update status date for all of them one by one mounthly
so I'm looking for a solution (probably VBA) for opening all projects and set the status date to a specified value and save & publish then check-in all of them.
is there any way to get it done?
thanks for any help

You can build a user form in VBA
I made one that has 12 text boxes with project names. It is used to open and close and republish projects to current date as status date but you could just as easily set that date to something specific.
Dim controlplanname
If TextBox1.TextLength <> 0 Then
    controlplanname = "<>\" & Trim(TextBox1.Text)
    FileOpenEx Name:=controlplanname, ReadOnly:=False
    Macro Name:="AfterAcceptControlPlanUpdates_Close"
End If
Sub abAfterAcceptControlPlanUpdates_Close()
' this is a first attempt at a one button macro
' after countless control plans are opened from the web
    'DisplayAlerts = False
    Alerts False
        Call WriteProjectDeadlineToFinalMilestone
        LevelingClear All:=True
        UpdateProject All:=True, UpdateDate:=Now, Action:=2
        Application.RepublishAssignments False, pjPublishScopeAll, False, True, True, ""
        fnWait (2)
        UpdateProjectToWeb EmbedProjectFile:=True
        'MailSendProjectMail MessageType:="TeamPublishAll", Subject:="Publish New and Changed Assignments", Body:="Below are the latest schedule changes. Contact your project manager if there are any problems with the changes.",
ShowDialog:=False, PublishScope:=1
    Alerts True
    fnWait (2)
   'DisplayAlerts = True
    FileClose pjSave
End Sub
So you could build a looping construct that finds out the status date of projects and if it is below a certain threshold then call the Sub.
It is important to also be aware that this sub will overwrite and not process the updates the resources have submitted.
My use case is accept all updates from PWA, All those projects open themselves. Then I apply the Sub. Then I have a list of Projects that have not been modified recently. And call the Sub separately on those via the custom form, and just let it run.

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

Segment E1EDP36 not active in the DELFOR02 IDOC type.

Hi All,
I have been working with creating extensions for Idoc type DELFOR02 inn ECC 6.0. But for the basic idoc type DELFOR02 , the segment E1EDP36 is not active here.i.e., the idoc generated does not carry data for this particular segement.
This segment depends on entries in a structure xisautoeklwes ( include LEINMF3S, line 130). The underlying table for this structure would be ISAUTOEKLWES(Last Deliveries for FLAB).
Could anyone throw light on how this structure will be filled or how it has to be filled if I can make changes to the customer exit available there.
Thanks,
Savitha Patil

Hi Gearge,
To add custom segments, you should create an extension.
the TCODE is we30.
Refer this link:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

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.

ORDERS05 Idoc Type Extension

Hello,
I am extending the segment E2EDKA3 in ORDERS05. Please let me know any user exit or any other way to populate the values in the extended segments.
I am adding these fields: VBPA-KUNNR,VBPA-ADRNR,VBPA-XCPDK & VBPA-ADRNP                         .
Thanks in advance,
Suresh

Hi Suresh,
Go through this info ucan able to do.
Enhancement of IDoc Type
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.
Let us take a scenario and understand the process of IDoc extension.
In this scenario say visitor is different from the actual customer who has came to the sales office in behalf of the customer to obtain the quotation or inquiry etc. Or an authorized agent qualified by the actual customer to order for items. So a field by name NAMEVI (Visitor) is added to Customer master data. As there is no provision given by SAP to handle this, we need to extend an IDoc.
The standard message type and IDoc type provided by SAP are DEBMAS and DEBMAS05.
Consider the data in the table below for extending the IDoc. These details can be understood in different sections in the process of extending it.
Basic IDoc type      DEBMAS05
Version      4.7
IDoc extension      DEBMASEXT
Custom segment      Z1KNA1
Fields in Custom Segment      Visitor
Parent of Custom Segment      E1KNA11
Outbound process
Step1. Customize kna1 table by appending a structure provided by SAP (ZAKNA1)
Component                Component Type
VISITOR                     NAMEVI
Step2: Write a module pool program to update some existing customers to add data for Visitor.
Step3: Create a custom segment
Transaction Code: WE31
Segment type: Z1KNA11   Click (create). Provide short text
Field Name                Data element
VISITOR                NAMEVI
Save
Step4: Create IDoc extension
Transaction      WE30
Object Name      DEBMASEXT
Choose Extension
Click   and it leads to next screen.
Linked basic type: DEBMAS05
Provide description and enter
Observe all the segments to be copied into your IDoc extension from linked basic
type.
Select E1KNA11 and click (create segment) to obtain a popup window
Provide the required values and observe child segment Z1KNA11 to be added to
parent segment E1KNA11.
Step5: Release segment and IDoc extension
Transaction: WE31
Segment type: Z1KNA11
Path: Edit à Set release
Step6: Assign Basic type to extension / messages
Transaction: WE82
Click , then
Select DEBMAS message type against DEBMAS06 basic type
Click   provide the information
Message Type      Basic Type      Extension      Version
DEBMAS      DEBMAS06      DEBMASEXT           4.7
Delete the earlier one from which it was copied.
Save.
Observe the result as follows
Step 7: Check and Transport IDoc extension
Transaction: WE30
Object name: DEBMASEXT
Path: Development object à Check
Ensure that there are no errors or warnings
Now transport
Path: Development à Transport
Step8: Find suitable user exit for writing code to support IDoc extension
Transaction: SE84.
Click Enhancements
In short text provide customer
Find suitable enhancement to be VSV00001
                         Alternative way
Transaction: SMOD
Click F4 help for Enhancement
Path: F4help à SAP Applications à Logistics general à Logistics Basic Data à
Business partners à Vendor Master.
Find the enhancement as VSV00002, which is an approximate user exit.
Now search for different extensions like VSV00001. Then see for its components.
Identify the appropriate user exit to be EXIT_SAPLVV01_001 (Create Export of
Additional Customer Master Segments). This user exit can be used in outbound ALE
process, meant for filling the data into custom segments.
You have to identify here another user exit as EXIT_SAPLVV02_001, which is
helpful for inbound ALE process. This user exit can be used to read the segments
and post it to Application repository.
Step9: Develop a project to encapsulate enhancements and components.
Transaction: CMOD.
Enhancement: custex and click Create to provide attributes.
Click Enhancement Assignments.
Provide VSV00001, short text and save.
From the initial screen of the transaction, select components and click change.
Find 4 components to be added.
Activate them.
Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
Double click on provided include program ZXVSVU01 and press enter.
Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
Check the code and activate.
Code in ZXVSVU01
*& Include           ZXVSVU01                                         *
*In this scenario, the E1KNA11 has been extended to accommodate
*User-defined fields in the customer table kna1. The name of the
*extended
*segment is z1kna11. There is one custom field: visitor
*Data declarations
DATA: kna1m like e1kna1m,
      kna11 like e1kna11,
      z1kna11 like z1kna11,
      w_kna1 like kna1.
make sure you are processing correct message type
check message_type eq 'DEBMAS'.
make sure data is added after the correct segment
check segment_name eq 'E1KNA1M'.
since customer number is not passed in this user exit, you need to go
through the data records to find the customer number
loop at idoc_data.
case idoc_data-segnam.
     when 'E1KNA1M'.
       move idoc_data-sdata to kna1m.
     when 'E1KNA11'.
       move idoc_data-sdata to kna11.
endcase.                             " case idoc_data-segname.
endloop.                               " loop at idoc_data.
select data from the user-defined fields in kna11.
select single *
from kna1                            " Customer master table
into w_kna1
where kunnr = kna1m-kunnr.
if sy-subrc eq 0.
set the idoc extension name for control record
idoc_cimtype = 'DEBMASEX'.
clear custom fields from kna1 to extended segment
clear z1kna11.
copy custom fields from kna1 to extended segment
move-corresponding w_kna1 to z1kna11. " field name must be same
condense all fields of extended segment
condense: z1kna11-visitor.
populate segment name in the data record, copy data contents into it
and append the data record to existing data records in
move 'Z1KNA11' TO IDOC_data-segnam.    " administrative section
move z1kna11 to idoc_data-sdata.       " data section
append idoc_data.
endif.                                 " if sy-subrc eq 0.
Step 10:
Define Logical System
Assign client to Logical System
Maintain RFC Destination
Maintain Customer Distribution Model
Generate Partner Profiles
Distribute Customer Distribution Model
INBOUND PROCESS
Step 11: Append the custom structure to the table KNA1 similar to the process done
        in outbound process.
Step 12.
Define Logical System
Assign client to Logical System
Generate Partner Profiles
Step 13. Execute the transaction to Send Customers from Outbound system.
Step 14. Now in the Inbound system, create the project in the similar way as done at
        outbound side.
In the user exit EXIT_SAPLVV02_001, find include ZXVSVU02. Write the code to
support IDoc extension.
Code in ZXVSVU02
*& Include           ZXVSVU02                                         *
data: kna1m like e1kna1m,
      kna11 like e1kna11,
      z1kna11 like z1kna11.
data fs_kna1 type kna1.
message i000(0) with 'INBOUND PROCESS CALLED'.
LOOP AT IDOC_data.
case idoc_data-segnam.
    when 'E1KNA1M'.
      kna1m = idoc_data-sdata.
    when 'E1KNA11'.
      kna11 = idoc_data-sdata.
    when 'Z1KNA11'.
      z1kna11 = idoc_data-sdata.
      select single *
        from kna1
        into fs_kna1
       where kunnr = kna1m-kunnr.
      if sy-subrc eq 0.
        update kna1
           set visitor = z1kna11-visitor
         where kunnr = kna1m-kunnr.
      else.
        idoc_status-docnum = idoc_control-docnum.
        idoc_status-status = '51'.
        idoc_status-msgty = 'E'.
        idoc_status-msgid = 'ZE'.
        idoc_status-msgno = '005'.
        idoc_status-msgv1 = kna1m-kunnr.
     append idoc_status.
      endif.                           " if sy-subrc eq 0.
endcase.                             " case idoc_data-segnam.
endloop.                               " LOOP AT IDOC_data.
Step 15. Assign FM to extension/Message type
Transaction:      WE57
Path: Change à New Entries
Select IDOC_INPUT_DEBITOR against DEBMAS06 basic type, to fill extra
information as shown below.
Function Module          Basic Type     Message Type          Extension
IDOC_INPUT_DEBITOR     DEBMAS06     DEBMAS          DEBMASEXT
Step 16. Execute the transaction to Get Customers.
And observe that records with extra data are saved in database.
Rewards some points.
Rgds,
P.Nag

Multiple message types for an idoc type

Hi all,
I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types
if it is so pls tell me how to assign these two message types for my idoc .
i want to create multiple message types because i want to send same idoc type to diff legacy systems.
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

Hi Kunal,
Below are my thoughts from a design perspective,
My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments
Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.
Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.
For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders
but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.
OR
Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.
Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).
how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?
The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.
You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.
I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.
Regards,
Chen

Basic idoc type for asset creatioon and asset acquisition

Hi
Please can anybody tell me the basic IDOC type provided by SAP for
- Asset creation
- Asset acquisition.
Thanx in advance....

Hi,
Go through this link
http://www.sap-basis-abap.com/fico/configuration-in-asset-accounting.htm
help.sap.com/bestpractices/BBLibrary/documentation/B44_BB_ConfigGuide_EN_Nordics.doc
Reward points if found helpful...
Cheers,
Chandra Sekhar.

Idoc Type for Organization Data

Hi,
I need to send Organization Data details through Idoc, those are
        Company Code
        Controlling Area
        Business Area.
Can anybody give IDOC type for above requirement. Thanks inadvance.
Regards,
Venkat

Dear Mohan,
Thanks for your valuable time and information.
That Idoc type u given is for Cost Centre master data. We found this through T.code BD16.
Can you give info Reg. Company Code, Business Area etc.
Regards,
Venkat

How to retrieve all the data from a BLOB using view-generated accessor

I am using JDeveveloper 10g v. 10.1.3 and am storing an image in a database as a blob object and need to retrieve all of the data to get the entire image and store it in an ImageIcon. The code I have works partially in that it retrieves the correct data, but only gets a piece of it, leaving me with a partial image.
AppModuleImpl am;
ImageVwViewImpl vo;
am = (AppModuleImpl)panelBinding.getDataControl().getDataProvider();
vo = (ImageVwViewImpl)am.findViewObject("ImageVwView");
ImageVwViewRowImpl ivo = (ImageVwViewRowImpl)vo.getCurrentRow();
ImageIcon icon = new ImageIcon(ivo.getImage().getBytes(1, (int)ivo.getImage().getBufferSize()));
jULabel1.setIcon(icon);I either need to know how to use a stream to get the data out (from BlobDomain method getBinaryStream()), or how to get the other chunks of data separately.
edit: I know the problem is that getBufferSize() returns an int which is too small to hold all the data, but need to know what to use instead. Thanks!

This is the code I'm using now. Same problem :(
AppModuleImpl am;
        ImageVwViewImpl vo;
        am = (AppModuleImpl)panelBinding.getDataControl().getDataProvider();
        vo = (ImageVwViewImpl)am.findViewObject("ImageVwView");
        ImageVwViewRowImpl ivo = (ImageVwViewRowImpl)vo.getCurrentRow();
        ImageIcon icon = new ImageIcon(ivo.getImage().toByteArray());
        jULabel1.setIcon(icon);

New pc how do i get all the data from my old pc to the new one

ok i have app music and video all on my old pc how do i transfer the whole lot to the new pc

You move it.
Windows provides a utility to move all user data from an old computer to a new computer, use it.

How can create SEGMENTS and IDOC TYPE in BADI in ECC 6.0 version

Hi All,
Can any one help, how to create SEGMENTS and IDOC TYPE in BADI in ECC 6.0 version.This is my task.
Given BADI name was----VENDOR_ADD_DATA_BI .
Thanks

Anil,
look at this thread ..may be this helps you.
Re: 824 IDOC and BADI/User Exit
sateesh.

Idoc type provided by ECC to hold all project data

Similar Messages

Maybe you are looking for