Creating message type in XI with imported objects

Hi,
I have imported an Idoc Structure into XI.
Now I need to create a message type with structure from imported Idoc + some additional fields.
Can some one tell me how to go about this. Because once I drag and drop the imported Idoc structure, I doesn't allow me to add any more fields during message type creation.
Is there a different to way to achieve this.
Best Regards,
Kiran

Hi Kiran,
the Integration Builder supports two ways of modelling an interface. The first way is to build the required datatypes from scratch (with the datatype editor) then define (fault) message types using these datatypes and finally define the message interface.
The second way is to use an externally defined structure by importing an IDoc or RFC from an R/3 or an external DTD/XSD/WSDL from filesystem. Then define your Message Interface using the messages from the imported objects.
Currently there is nearly no support for mixing these two approaches as you have in mind (taking an externally defined structure as starting point, then enhance this structure within the Integration Builder).
The best workaround I can suggest to you, is import the IDoc, take the XSD which is displayed for it, download it to your local file system, edit it there (with notepad when you are an XSD expert, with some other tool like XML Spy otherwise) and upload the modified file as External Definition.
BTW: For this procedure you do not necessarily need to upload the IDoc to the Repository. As far as I know the R/3 also offers the possibility to generate an XSD representation for an IDoc (do not remember the exact way to go there).
Greetings Stephan

Similar Messages

Creating Message Type

what are the possible way to create message type and how you link the message type with idoc type.
Thanks in Advance....

Hi Senthil,
There is a transaction code for link the message type to the idoc type using the T.code we82.
There we can assign the our own message type and Idoctype (basic type) we can assign. If u want to extension the basic type we have the option and we must release it.
********rewords some points if it is helpful.
Rgds,
P.Naganjana Reddy

Bapi for creating message type in a sales order

Hi, I am involved in a IS-MAM project for an italian company.
I need to create or add a message output type in a sales order in a complex batch program. I thought to use a bapi technicality; in particular BAPI_ADMGMTSO_CHANGE in order to change the document.
How can I create message type in the order? Can I use the same bapi or I need of an other one?
thanks in advance for your help
Lucia

Can you please provide more information...

What is the Technical Reason for Creating Message Type

Hi,
Is there any particular reason to use Message Type. Already we are defining Data Type. Please give me some detailed explanations.
Thanks in Advance.
Thanks & Regards,
Giridhar.C

Hi Giri,
SAP telling below reason why we are creating message type
"A message type comprises a data type that describes the structure of a message. For technical reasons, a data type alone is not sufficient to describe the instance of a message: Data types are defined in XML Schema as abstract types that are not yet tied to an element. You can only describe an instance of a message when you have specified a data type as an element type. Therefore, a message type defines the root element of a message"
Regards,
Raj

Ale with user created message type

Hello,
I have a created a segment ,idoc and message type and done the assignment of Idoc with message type also.
i have to send the material 800 to 810 client through ALE.
By using the Standard Message type MATMAS i m getting the material on 810 client.
But when i am using my message type ie ZMAT_MSG in tcode BD10 on client 800 to send the material it is saying error that message type does not exist.
I am not getting the problem
Or it is not possible to use your message type to send the material through Tcode BD10.You have to always use the standard message type MATMAS.
If yes then how to use our own message type to transfer the data from client 800 to 810.
Please reply .
Manish

Hi Vasu,
Please try this.
1. Create distribution model (BD64) for message type MATMAS_BAPI.
2. Create inbound partner profile (WE20) for message type MATMAS_BAPI and IDoc type MATMAS_BAPI01 and process code BAPI.
3. Create IDoc ports (WE21)
4. Setup RFC destination (SM59).
Hope this will help to start with.
Regards,
Ferry Lianto
Please reward points if helpful.

Http 403 when creating message type

Hi,
I have a bpel process that invokes a secure web service (https://....?wsdl). To be able to create the partner link and execute the process, I had to copy the certificate in two directories and import the certificate in jdeveloper and soa suite.
So, now I'm able to invoke the secure web service. The problem appears when I want to create a new Message Type using the secure web service. I try to choose the ws types and this error appears: "Error reading message parts! HTTP connection error code is 403"
I tried creating my own schema but when using xpath expression there are problems with the namespaces. So I would need to create the variable using the original wsdl.
Does anybody know what is happening? How can I solve this issue?
Thanks in advance,
Zaloa

Installed tamper data and from what I can tell, the requests go back and forth between AM server and protected resource. Here's the Request Graph output.
http://iamsys06.iamtest.com:8080/ 302 103
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 16
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 200 16
http://iamsys05:9080/favicon.ico 404 50
http://iamsys05:9080/.../Login?AMAuthCookie=AQIC5wM2LY4Sfcz... 302 183
http://iamsys06.iamtest.com:8080/ 302 30
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 17
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 302 10711
http://iamsys06.iamtest.com:8080/ 302 23
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 15
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 302 16
http://iamsys06.iamtest.com:8080/ 302 18
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 17
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 302 13
http://iamsys06.iamtest.com:8080/ 302 13
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 10
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 302 10
http://iamsys06.iamtest.com:8080/ 302 16
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 11
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 302 12
http://iamsys06.iamtest.com:8080/ 302 12
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 10
http://iamsys05:9080/.../Login?goto=http%3A%2F%2Fiams... 302 12
http://iamsys06.iamtest.com:8080/ 302 12
http://iamsys05.iamtest.com:9080/.../Login?goto=http%3A%2... 302 10
| | | | |
URI Status Duration 20:59:52.542 20:59:56.512 21:00:00.482 21:00:04.451 21:00:08.421

Transaction/Program to create message type LIP076 Idocs

Hi Idoc Experts,
Can you please let me know the T-code/program to send MD61(weekly forecast) data thru the idocs.
FYI- I am planning to use message type LIP076 with basic type SOPGEN01
Example: BD14 T-code to send the Vendor master details thru idoc.
I am looking for a similiar transaction/program, so that it will create LIP076 idocs with MD61 details.
Thankyou,
Ravi

Hello Ravindran
You can also check the documentation in the below path and when you execute it it takes you to transaction SXDA. I am not authorized in my system, may be you can check more detailed in your system about the transaction..
SPRO -- > IMG --> Production --> Production planning --> Demand management --> tools --> Data transfer workbench: planned independent requirements.
Regards,
Thanga

Why do we create message types (we81)?

Hi Guys,
Could u plz explain me for wht purpose message types r created?
thanking u...
regards..

hi
good
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
hope this will help you.
Thanks
mrutyun^

How to create a feather-like drop with an object?

Hello,
I am looking for a feather-like drop with an object?
I am using AECS3.
Anyone have a good tutorial and/or method?
Thanks,
Simon

Ah, sorry, I assumed too much. CC Cylinder requires a small object on a large layer. There are no ballistics settings for any of this feather stuff, you create it.
Draw a storyboard of your motion path, what does this falling object do and where does it go on the screen?
Does it swoop and pause? Imagine a falling leaf. Suggest you buy a copy of FORREST GUMP to deconstruct the feather animation effects.
Draw that motion path using position keyframes and remember that to create a pause at the top of an arc you need two keyframes.
(You can complicate this by using a 3D space so your feather moves toward and away from the camera but this can be simulated by scaling your cylinder layer.)
When you get the movement roughed out, you can start playing with the rotation settings for the cylinder object. You will attempt to orient the intrinsic movement of the cylinder with the implied air currents and directional changes. For instance, if the feather is climbing an arc, the rotation will follow the trajectory but at the top of the arc, the feather will pause while the rotation flips it over and then it accelerates in a fall as the feather points downward.
This isn't easy. Nothing in After Effects is easy. But it's direct an fairly intuitive when you start thinking about what a light object will do when it becomes a glider. You just need to understand the implied physics and ballistics. Attempting to make it "real" is likely to make the effect appear overworked.
I can send you a small project file. It's not polished at all, but will give you some idea of what you can play with. dbogieATidahopowerDOTcom replace the AT with "@" and DOT with "."
bogiesan

USE OF CREATING MESSAGE TYPES

PLZ TELL ME THE USE OF CREATING THE MESSAGE TYPES AND MESSAGE INTERFACERS?

Hi DHANUNJAY,
Message type: message type is the structure which holds our message at runtime. you declare the data type first for which you create a message type.
Message Interface: It can be of Outbound/Inbound/Abstract type and of Synchronous/Asynchronous mode.
message interface holds the message type. in the message interface level you can define the interface for source side(outbound) or target side(inbound).
The communication in XI is done in the Message Interface level(which is the Outer most level of communication).
Please reward.
Regards
Sankar

ODI Migration for 10.1.3.5 to 11.1.1.3 failed with Importing object

ODI Migration from 10.1.3.5 to 11.1.1.3 failed
DB Repositories -Oracle 11.1.0.7
I am trying to upgrade ODI 10.1.3.5 to 11.1.1.3 version
After running RCC and confirming that there are no issues I have run upgrade assistant utility
I am getting below error.
mporting file:/E:/Oracle/Middleware/Oracle_ODI1/oracledi.sdk/lib/scripts/xml/CONN_MEMORY_ENGINE.xml
[2012-05-02T06:17:27.770-07:00] [ODI] [INCIDENT_ERROR] [UPGCMP-00324] [upgrade.ODI] [tid: 14] [ecid: 0000JSDg06MF^6WFLzmJOA1FcIg5000005,0] Topology and Security Metadata upgrade failed.[[
oracle.odi.core.exception.OdiRuntimeException: com.sunopsis.tools.core.exception.SnpsSimpleMessageException: Importing object SNP_CONNECT : SUNOPSIS_MEMORY_ENGINE failed.
     at oracle.odi.impexp.support.ImportServiceImpl.internalReimportTopologyReferenceData(ImportServiceImpl.java:1372)
     at oracle.odi.impexp.support.ImportServiceImpl$18.doAction(ImportServiceImpl.java:1435)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:193)
     at oracle.odi.core.persistence.dwgobject.TransactionalDwgObjectTemplate.execute(TransactionalDwgObjectTemplate.java:48)
     at oracle.odi.impexp.support.ImportServiceImpl.reimportTopologyReferenceData(ImportServiceImpl.java:1429)
     at oracle.ias.mrua.plugin.odi.ODIPlugin$1.doInTransaction(ODIPlugin.java:774)
     at oracle.odi.core.persistence.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:119)
     at oracle.ias.mrua.plugin.odi.ODIPlugin.doUpgrade(ODIPlugin.java:770)
     at oracle.ias.mrua.MRUA.executePlugins(MRUA.java:3703)
     at oracle.ias.mrua.MRUA.internal_driver(MRUA.java:2465)
     at oracle.ias.mrua.MRUA.driver(MRUA.java:1734)
     at oracle.ias.upgrade.gui.UAUpgradeThread.run(UAUpgradeThread.java:390)
Caused by: com.sunopsis.tools.core.exception.SnpsSimpleMessageException: Importing object SNP_CONNECT : SUNOPSIS_MEMORY_ENGINE failed.
     at com.sunopsis.dwg.DwgDuplicationTools.importOtherObjects(DwgDuplicationTools.java:2379)
     at com.sunopsis.dwg.DwgDuplicationTools.synonymImport(DwgDuplicationTools.java:1835)
     at com.sunopsis.dwg.DwgObject.importFromObjectLst(DwgObject.java:6249)
     at com.sunopsis.dwg.DwgObject.doImport(DwgObject.java:5705)
     at com.sunopsis.dwg.DwgObject.importFromXml(DwgObject.java:5365)
     at com.sunopsis.dwg.DwgObject.importFromXml(DwgObject.java:5334)
     at com.sunopsis.repository.manager.RepositoryManager.importObjectsUsingImportFromXML(RepositoryManager.java:6578)
     at com.sunopsis.repository.manager.RepositoryManager.treatObjectList(RepositoryManager.java:4630)
     at com.sunopsis.repository.manager.RepositoryManager.reimportTopologyReferenceData(RepositoryManager.java:6820)
     at oracle.odi.impexp.support.ImportServiceImpl.internalReimportTopologyReferenceData(ImportServiceImpl.java:1368)
     ... 11 more
Caused by: com.sunopsis.dwg.SQLMasterReposException: ORA-00001: unique constraint (ODIM.AK_CONNECT) violated
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1009)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1315)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3657)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
     at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java:665)
     at com.sunopsis.dwg.dbobj.generated.GeneratedSnpConnect.insertAction(GeneratedSnpConnect.java:957)
     at com.sunopsis.dwg.dbobj.SnpConnect.insertAction(SnpConnect.java:1188)
     at com.sunopsis.dwg.DwgObject.insertActionForDuplication(DwgObject.java:2996)
     at com.sunopsis.dwg.DwgObject.insertForDuplication(DwgObject.java:3274)
     at com.sunopsis.dwg.DwgDuplicationTools.importOtherObjects(DwgDuplicationTools.java:2332)
     ... 20 more
[2012-05-02T06:17:29.895-07:00] [ODI] [INCIDENT_ERROR] [] [upgrade.ODI] [tid: 14] [ecid: 0000JSDg06MF^6WFLzmJOA1FcIg5000005,0] [[
--------- ODIPlugin.doUpgrade called org.springframework.transaction.TransactionSystemException: Could not commit ODI-JPA transaction; nested exception is javax.persistence.RollbackException: Transaction rolled back because transaction was set to RollbackOnly.
Caused by: javax.persistence.RollbackException: Transaction rolled back because transaction was set to RollbackOnly.
     at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commitInternal(EntityTransactionImpl.java:92)
     at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:63)
     at oracle.odi.core.persistence.jpa.JpaOdiTransactionManager.doCommit(JpaOdiTransactionManager.java:362)
     at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:651)
     at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:622)
     at oracle.odi.core.persistence.transaction.support.TransactionManagerSpringAdapter.commit(TransactionManagerSpringAdapter.java:56)
     at oracle.odi.core.persistence.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:132)
     at oracle.ias.mrua.plugin.odi.ODIPlugin.doUpgrade(ODIPlugin.java:770)
     at oracle.ias.mrua.MRUA.executePlugins(MRUA.java:3703)
     at oracle.ias.mrua.MRUA.internal_driver(MRUA.java:2465)
     at oracle.ias.mrua.MRUA.driver(MRUA.java:1734)
     at oracle.ias.upgrade.gui.UAUpgradeThread.run(UAUpgradeThread.java:390)

I also want to do the ODI Migration for 10.1.3.5 to 11.1.1.3, can you let me know your detail steps, many thanks in advance.

Do we need to create message interfaces for idocs and rfcs thatare imported

do we need to create message interfaces for idocs and rfcs thatare imported
from sap server
in scenarios from sap system to file or vice versa
i knew that we need not create message types
do we also skip creating message interfaces

hi,
you create an abstract message interface for IDOC only if you want to use
them in a BPM (integration process)
for more about IDOCs have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

How to create a message type

Hi, All
I need to create a message type, Enter the fields change pointers eligible for key changer in this message type. Extract program needs to be created and this program accesses the key changer fields status and the changed values on day to day basis for the message type using tables BDCPS & BDCPV.
Can any one tell me how to do this.
Many Thanks.

Hello siri
I think if you talking with respect to ALE/IDOC or EDI/IDOC..........this posting has to be entered in data transfer.........................and you can create message type using trasaction we81.
Vj

How to main the message type is I for the exceptions when we create the FM

HI ,
I have created one FM.in that i need to maintain the exceptions. for handling the exceptions message type is I.
where can i maintain the exceptions message type I.is it at the creation of FM or calling of FM?
tell me in details.
for handling exceptions:
No Sales Order Created = Message type 'I'
OTHERS = Message type 'I'
thanks in advance

Exceptions are only code and text, the kind of message comes from the raising statement in the FM code.
RAISE <Exception>.
MESSAGE..... RAISING <Exception>.
The management of the resulting code is in the caller program. ([Calling Function Modules From Your Programs|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801edb454211d189710000e8322d00/frameset.htm])
     EXCEPTIONS
          no_values_found = 1
          ERROR_MESSAGE   = 2
          OTHERS          = 3.
CASE SY-SUBRC.
WHEN 1.
I don't understand your requirement, try to read some documentation like [Specifying Parameters and Exceptions|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801ee8454211d189710000e8322d00/frameset.htm] in [Function Builder|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801e9a454211d189710000e8322d00/frameset.htm] and reformulate please.
Regards,
Raymond

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.

Creating message type in XI with imported objects

Similar Messages

Maybe you are looking for