Idoc Types with customer extension in XI

Hello,
I have a question / problem.
Is it possible to import an IDOC Type like HRMD_A06 with an customer extension like ZRMD_A06 into XI ?
I have no idea how that could works ...
Thanks for your feedback !
Regards
Florian

Hi,
You can import IDoc structure with extensions also. It will be same as importing normal idoc structure.
We have done many like that in our project.
What is the problem you are facing ?
Regards,
Sridhar

Similar Messages

Want to add multiple idoc type with single message type.

Hi Gurus,
I have a problem. I want to add multiple idoc type with single message type in WE20.
How we can do this in WE20 or is there any other way to do that?
Please help me.
Thanks in advance.
Srimanta.

hi,
basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
so what exactly we do in that is that we first use the message type for those idocs that we have created.
now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
it will solve your problem.
hope this will help you!!!
Thanks & regards,
punit raval.

Interaction of Marker list with custom extensions.

Hi,
How I can interact the marker list with custom extension.
For example if I want to see the file name and mark in mark out time codes in my custom panel, then what I need to do?
Please help me regarding this.
Thanks in advance.

Extension Manager is only responsible for the installation and management of extensions. Your question is about how to implement the functionalities of your extension. I am not clear about it. I am afraid you should post the question to the forum of corresponding product.

Idoc ORDERS05 with Custom Message Type

We want to use a Z message type for idoc type ORDERS05 to be able to separate a particular group of partners from other partners using ORDERS/ORDERS05.
The goal with our Z message type is to use the standard function IDOC_OUTPUT_ORDERS. The only problem I see is that this function checks the message type in form READ_SERVICE_PACKAGE. It would ignore this code since my message type is a Z and it's checking for message type ORDERS.
I was thinking of using a Z wrap-around function to perform the same code in form READ_SERVICE_PACKAGE if the message type is my Z message type.
I want to avoid creating a Z copy of IDOC_OUTPUT_ORDERS and all if the includes!!!
Any suggestions?

Hello Bruce,
The function module is associated with the process code.
Why do you need a new message type?
Regards,
Samir.

IDOC type for customer master

Hi friends,
Could anyone explain me about...

Use existing IDOC types to send the customer master data, vendor master data and material master data from the sender system to the receiver system.

Hi,
Please maintain distribution model (BD64) and partner profile (WE20), RFC connection (SM59) for message type DEBMAS (customer), DEBMAS (vendor) and MATMAS (material master).
Once the above configuration done, then you can use the following transactions to send the IDocs.
1. BD12 - Send Customer IDocs (Sender -> Receiver) or
 BD13 - Get Customer IDocs (Receiver -> Sender)
2. BD14 - Send Vendor IDocs (Sender -> Receiver) or
 BD15 - Get Vendor IDocs (Receiver -> Sender)
3. BD10 - Send Material IDocs (Sender -> Receiver) or
 BD11 - Get Material IDocs (Receiver -> Sender)
Regards,
Ferry Lianto

Message Type ( Idoc Type ) for customer master & Pending invoice

Hi
My Client is doing sale in POS for credit customers and credit customer master should be sent to POS as outbound Idoc.
1.What is the standard message type for sending Customer masters to POS. WP_PER01 is not activated for version 700 ( message getting on WE60 ). Plse let us know is there any another message type for customer master.
2. Also i need to send the credit limit of the customer to POS . Is this possible by standard message type or we need to go for ZIdoc?.
3.Is there standard Outbound Idoc ( Message type ) available to send the Pending invoice list toPOS?
plse help me on the above
Regards
Anis

Hi ,
you can use DEBMAS message type for customer master IDOC ,
Tcode Bd12
Thanks,
Amit

Using multiple node types with and Extension Handler

I'm tailoring the example BasicExtensionHandler.jsx provided in the CS4 SDK to fit my file structure needs. Being new to scripting bridge, I have experimented with limited success.
In a separate script, I have learned how to make a new thumbnail from a URI to be added to my Favorites, and it will add with or without the bridge:fs: prefix. I am not entirely clear when to use the path instead of the URI. Is the difference between a path and a URI the prefix?
var t = new Thumbnail("bridge:fs:file:///Users/username/Desktop/2010SampleLibrary/Job1/Graphics/logo1 .ai");
Using the ExtensionHandler, I understand how to add containers and leafs to create the file heirarchy that want.
var root = new SDKNode("BERoot", true);
var sub = new SDKNode("EHFolder1", true)
root.addNode(sub);
var sys = new SDKSystem("bridge:beNode:");
sys.addRoot(root);
What is the next step for adding the file referenced in the thumbnail of the first script fragment to the node structure referenced in the extension handler of the second script fragment? Do I create a new node with the path or URI specified, and add it as a child to a parent folder? (script presumes that I've properly redefined the SDKNode.jsx to accept the first parameter passed to it as the path)
var n = new SDKNode ("file:///Users/username/Desktop/2010SampleLibrary/Job1/Graphics/logo1.ai", false);
d = root.findChildNode("EHFolder2");
d.addNode(n);
I suppose this is one of the more elementary problems that everyone here learned during the first day of Computer Science class, but alas, I'm an artist.I understand that the BasicExtensionHandler.jsx does not have any real functionality... I'm addressing that later after I learn the syntax for creating my own virtual file structure that will be populated with select files from a much larger library of files.
Thanks for the help, samples appreciated.

I have a project that I have created for a web application. Within the web application, there are 3 types of customers (Commercial Accts, National Accts, and Tier 1 Customers).
I have tagged each help topic that is associated with the help topics I have created.
Then, I created 3 webhelp outputs and 3 TOCs for each customer type.
My goal is to publish the project, where each customer type has their own generated output. Doing it this way, what is listed in the TOC help topics for each customer type is not displaying correctly.
Example: National Accounts TOC
What is generated:
Please help. Any advice? I can also be reached at [email protected]

Sending E-Mail with ABAP List as Attachment with custom Extension

Hello everyone.
I have the following problem:
I want to send a ABAP list as an attachment to an external e-mail address with a custom file extension.
Everything works fine, exept the thing with the file extension.
I am using FB 'SO_NEW_DOCUMENT_ATT_SEND_API1'.
When I choose 'ALI' as Packing_List-Doc_Type everything works fine, but the attached file has the extension 'txt'.
When I choose e.g. 'lbl' as Doc_Type, the extension is correct, but the file contains invalid data.
Packinglist code:
AttType = 'ALI'.
Describe Table ObjBin Lines TabLines.
Read Table ObjBin Index TabLines.
ObjPack-Doc_Size = ( TabLines - 1 ) * 255 + strlen( ObjBin ).
ObjPack-Transf_Bin = 'X'.
ObjPack-Head_Start = 1.
ObjPack-Head_Num = 1. "0.
ObjPack-Body_Start = 1.
ObjPack-Body_Num = TabLines.
ObjPack-Doc_Type = AttType.
ObjPack-Obj_Name = 'ATTACHMENT'.
ObjPack-Obj_Descr = cFileName.
Append ObjPack.
function call:
Call Function 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 EXPORTING
 Document_Data = DocData
 Put_in_Outbox = 'X'
 TABLES
 Packing_List = ObjPack
 Object_Header = ObjHeader
 Contents_Bin = ObjBin
 Contents_Txt = ObjTxt
 Receivers = RecList
 EXCEPTIONS
 Too_Many_Recievers = 1
 Document_Not_Sent = 2
 Document_Type_Not_Exist = 3
 Operation_No_Authorization = 4
 Parameter_Error = 5
 X_Error = 6
 Enqueue_Error = 7
 Others = 8.
Thanks for your help,
Arndt

Hi,
look here:
Re: How to email an attachment with more than 255 characters?
Andreas

FileSelectPopup, discriminate multiple types with same extension

Hi,
When using a file select popup with multiple file types of the SAME extension, such as:
FileSelectPopup ("", "(8 bit)*.tiff", "(8 bit)*.tiff;(16 bit)*.tiff", "Save As", VAL_SAVE_BUTTON, 0, 0, 1, 1, file);
Is there any way to know which "save as type" was selected by the user on the popup?
(win7x86; CVI 2010)
cheers,
Diz
Solved!
Go to Solution.

I dodn't focused on the "save" option enabled.
In such a situation I would design a small options panel with abutton to select the destination filename using FileSelectPopup, a radio button or a ring to discriminate the file format and usual OK and Abort buttons.
This unless you can determine the final file format from the origin of your data (i.e. if you are saving a 8bit image, use 8-bit TIFF format and so on, provided you must not perform format conversion during save).
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

How to create attribute & set types with customer namespace COMM_ATTRSET?

Hi CRM Gurus,
I want to create some attributes and set types on CRM system with
`/FITGL/` namespace but system is not allowed to create objects
according. After debugging derives that SAP standart coding given below
on LCOM_ATTRIBUTE_NEWF19 include.
IF ( lv_systemname <> gc_sap_system ) AND
( iv_object_name(1) <> 'Y' AND iv_object_name(1) <> 'Z' ).
Should we make an enhancement on this include? Is there any side
efffects of this enhancement creating attribute & set types on CRM
system during the packaging in terms of related with other attribute & set types objects?
Kind Regards,
Fahrettin

Hi CRM Gurus,
I want to create some attributes and set types on CRM system with
`/FITGL/` namespace but system is not allowed to create objects
according. After debugging derives that SAP standart coding given below
on LCOM_ATTRIBUTE_NEWF19 include.
IF ( lv_systemname <> gc_sap_system ) AND
( iv_object_name(1) <> 'Y' AND iv_object_name(1) <> 'Z' ).
Should we make an enhancement on this include? Is there any side
efffects of this enhancement creating attribute & set types on CRM
system during the packaging in terms of related with other attribute & set types objects?
Kind Regards,
Fahrettin

Basic IDOC types

what are these ORDERS05, DELIVERY03 & WMMBID02
i found that these are basic idoc types. what does it mean?
Regards,
pandu.

Some IDoc types are supplied by SAP in the standard system,
these are the basic types. Other IDoc types are customer
extensions. In these cases, a basic type is combined with
an extension which is created by the customer, according to
certain rules. Unlike customer extensions , these extended
basic types are upward compatible.
regards,
srinivas
*reward for useful answers*

How to copy one IDoc type

Hi guys!
I need to copy one idoc type with Z extension to another R/3 system. How to do it?
Thank you!
Olian

Hi,
You can transport the IDoc Type to higher boxes.
But I could not able to find anything download and upload option.
a®

Extending an IDoc Type or Creating Custom IDoc type

Hi Experts,
We need to modify IDoc Type "DESADV01" for adding extra fields. Should I extend this IDoc Type or Create a new Custom IDoc type with the extra fields? Which is the best practice? This is my first time with IDoc functionality. Please let me know.
Thanks for the help.

Hi Dev,
Simple solution man.
Try to create an extension for the Idoc you wanted to extend.
Steps would be as follows: -
1) Go to WE31, create the z-segments and make them ready
2) Go to WE30, give some name for the extension and select the radio button extension and click on create button
3) It will ask you necessary details like which idoc you wanted to extend...Give the details and add the z-segments and save it.
4) Release it
Thats it.
Hope this solves your problem.
Thanks,
Babu Kilari

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.

Outbound output type & Idoc type for MIRO (Invoice Posting)

Hi Gurus,
I have requirement like , I want to send the outbound IDoc to a external system containg the invoice detials after Saving in MIRO.
I am not able to find any output type & Idoc type for the same.
By going through varios threads , I found that there tell there is no Idoc type & output type for sending Idocs after MIRO.
Kindlt let me know, if it so, or how this req can be fullfiled by other ways.
Thanks
Amresh

Hi,
Create Custom Idoc type with required fields,custom output type and assign it to partner profiles.(If there is no std idoc type or output type)
Use Funtion module MASTER_IDOC_DISTRIBUTE to generate Idocs while saving MIRO, for this you need to find exit or implement implicit enhancement while saving MIRO.
Regards,
Ashok.

Idoc Types with customer extension in XI

Similar Messages

Maybe you are looking for