IDOC Type - TRXSTA01 is missing in 4.6 C

Hi ,
Though TRXSTA01 is supported by SAP . We are not able to find the same in 4.6 C
The following 'basic IDOC type' is not available .
IDOC Type: TRXSTA01
Message Type: TRXSTA
Process code: TRXS
Function Module: BORTE_IDOC_INPUT_TRXSTA.
The IDOC type is basically used for shipment status notification.
It seemes to be release issues .
Any help will be appriciated .
Regards
Samir

Hi Sameer,
Welcome to SDN.
Perhaps you can use this IDoc type and message type instead.
- DELVRY03/DESADV for shipping notification.
- SHPMNT05/SHPADV for shipment message.
For more information, please check this link.
http://help.sap.com/saphelp_erp2005/helpdata/en/25/42a5ca89bf11d288de0000e8214d78/frameset.htm
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Similar Messages

IDOC Types and their equivalent messages in EDIFACT and ANSI X12

Hi all, since I only have a list of messages in EDIFACT and ANSI X12 for release 4.6 B, I need to update the list from 6.0 version, but I don't have online support system to get it (OSS), it's note 104606 in OSS.
Can somebody give me a link to the full new updated list? Will surely give points with your helpful answers
Regards,

Hi,
Please check these perhaps they may help.
Mapping ANSI X12 to SAP Message Type and IDoc Type:
204 Motor carrier shipment information
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880), EDI - Inbound INVOIC posting configuration
The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELFOR, the IDoc type is DELFOR01.
832 Price catalog (also 879, 888, 889)
The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04. Outbound processing is supported.
850 Purchase order or order (also 875)
The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
The logical message is PROACT, the IDoc type PROACT01.
855 Ordering or order response (also 865)
The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
For delivery in the SAP application, the logical message is DESADV, the IDoc types are DESADV01 (expires) or DELVRY01 and DELVRY02.
860 Ordering or order modification (also 876)
The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
The logical message is GSVERF, the IDoc type GSVERF01.
862 delivery schedule (FAB)
The logical message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDoc type is DELFOR01.
864 Text message
The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional Acknowledgment
This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
"22" Shipping OK, acknowledgment has yet to come
"16" Functional Acknowledgment positive
"17" Functional Acknowledgment negative
The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.
Regards,
Ferry Lianto

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

Custom IDoc Type missing segment parent/child relationships

Hi.
I copied the standard ORDERS05 IDoc type to a custom type and cut out quite a few segments. My new IDoc type is setup with parent/child segment relationships, similar to many of the original relationships in ORDERS05.
When I use the standard FM IDOC_OUTPUT_ORDRSP to generate an IDoc, it's not creating with parent/child segment relationships. It's placing the children at the same level as the parent.
Anyone know what I'm doing wrong?
Thanks!
Cal

figured out the problem. was missing a required segment used to establish the parent/child relationship.

Error while creating an outbound idoc using idoc type delvry02

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

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

IDoc type could not be determined for the IDoc in F110

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

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

Modify BP in CRM using Idoc type BUPA_INBOUND_MAIN_SAVE_M03

Hi,
I want to modify(add) a new role to an existing BP in CRM.
I am using the Idoc type BUPA_INBOUND_MAIN_SAVE_M03 for the same.
The problem that I am facing is that even though I am wanting to modify the BP, whenever this IDoc is posted the existing roles (seen in table BUT100) for the BP get deleted and the new role is added through the interface.
Please can anyone assist me as what is going missing in the filling the segments.
Regards,
Taher
the segment structure is as below.
BUPA_INBOUND_MAIN_SAVE_M03
E101BUS_EI_EXTERN
E101BUS_EI_HEADER
        E101BUS_EI_INSTANCE
    E101BUS_EI_CENTRAL_DATA
        E101BUS_EI_ROLES
            E101BUS_EI_BUPA_ROLES
                E101BUS_EI_ROLE_DATA
                E101BUS_EI_ROLE_DATA_X

Hi,
I figured out the solution to this.
Get the existing roles for the BP using the FM BAPI_BUPA_ROLES_GET.
Append the existing roles along with the new role that is required to be added.
the task type should be I (Insert).
When the Idoc is posted the existing roles do not get overwritten and the new role is added.
Regards,
taher

Issues in using the GLMAST01 idoc type

Hi there,
           I am using the LSMW to upload the GL master records using the IDOC method. I am using the IDoc type as GLMAST01. I am passing the following data. I am not able to post the IDoc with following data. Please tell me, is there anything I am missing here or there is something else because of which I am getting the results?
         In E1SKA1M, I am passing the values for SAKNR, KTOPL, KTOKS, XBLIK, VBUND, BILKT.
         In E1SKATM, I am passing the values for SPRAS, TXT20 and TXT50.
        In E1SKB1M, I am passing the values for BUKRS, WAERS, FSTAG.
        In some cases, I am creating the multiple segments for E1SKATM and E1SKB1M segments.
        This is kind of getting urgent and I could not find the answers for this in any other post on SDN. Please help.
Thanks,
Ganesh V Khumse

Hi Vishnu,
There is no solution for this, you cannot have GUI interactions(nor any statements that might invoke a implicit/explicit commit) in a V2 update. When you say this worked, did you have update debugging enabled, if so then it might have worked as the debugger session can access GUI...
If the whole idea/need of this output is to download a file, use OPEN DATASET, TRANSFER and CLOSE DATASET.
Even for the RSNAST00 execution, i am sure that in the actual business scenario(in production) this would be scheduled as a background job, where in again "GUI_DOWNLOAD" wouldn't work.
Regards,
Chen

Collect Multiple IDOC(Single IDOC type) to single file using BPM

Hi All,
When i am generating multiple IDOC for the same message type, i am getting multiple payload for the same as a result i used to get multiple files generated in application server.
Now if i use BPM only to collect multiple IDOC to a file then what all the steps that i need to follow for the same.
Ex: I want to post 10 IDOC for a single IDOC type,, Now using BPM in XI i want to collect all the 10 IDOCs with multiple payload into one single message and then want to process this in XI to generate the file.
It would be glad if anyone refer me a good step by step blog for the same.
Thanks in advance,
Jay

Thanks a lot Abhisek.
I have also got a blog explaining the exact thing. But in the blog the ID part was missing which is present in the link you have provided.
I will be glad if you can through some light on the ID part,, however the IR part and the BPM part is now mostly okay to me.
I will configure this today only,, and may seek your help for any huddle.
Thanks a lot once again.
Regards,
Jay.

Extending IDOC type

Hi,
Iam using the business object BUS20001 (CRMXIF_ORDER_SAVE_M) to create service order in CRM 3.1 system using LSMW. We have an addfiled in the order hence extended the IDOC type (ZCRMXIF_ORDER_SAVE_M02B), creating a new segment and attaching to the IDOC type. When i look into this extended IDOC type in the transaction WE30, all the segments has mapped to a field in the structure CRMXIF_BUS_TRANS. But the newly created segment has no mapping. This unmapped field is not getting updated in the order created.
Do i have to extended the structure CRMXIF_BUS_TRANS when i extend the IDOC type.Please advise if i miss any steps in extending the IDOC type.
Regards
Dhanapal S

Hi Dhanapal,
When there is a change in IDoc structure, you need to re-import in Repository.
Also, in IDX1 transaction delete the existing meta data for the IDoc and import the meta data once again.
Regards,
Uma

Outbound idoc types in XI

I was creating partner profile using we20 in XI to send and receives idoc of type ORDERS and ORDRSP. In the outbound parmtrs section I am not seeing ORDERS type. I clicked the + sign under the outbound parmtrs, it opened a new page to create a outbound paramets. I did not see ORDERS message type, so I created a message type called ORDERS and ORDRSP using we81. When I came back, I do see the message type I created. Now, I need to select the basic idoc type in the outbound options but I am not seeing ORDERS or ORDERS05 to select. Why isn't XI have the basic IDOCs for ORDERS.
Am I missing something?

Hi,
WE81 is the transaction for creating Logical Messag types in SAP R/3. Since XI is one of the R/3 product, you have an option to create the message types.
normally, Partner Profiles are maintained for Business communication in R/3 using EDI media. I am not sure, if at all XI will be used as a business partner as it is a middle layer kind of environment giving an interface facility to R/3 to the outside environment.
Coming to your question, XI need not to have all the message types/IDOC types as we see in R/3. IDOC Type definitions will be downloaded into XI for making it available for data transmission using the transaction IDX2 and is also known as IDOC CACHE.
To be able to help you out, let us know your scenario in which you are using XI as a business partner.
Further, Default Outbound parameters will not be available when a partner profile is created. You have to assign the business rules to it so called MESSAGE TYPES, IDOC TYPES, PROCESS CODES, RFCDESTINATIONS/PORTS, PACKET SIZES, MESSAGE CONTROLS. etc.,
What have you done? You have created a message type ORDERS/ORDERSP thru WE81, but no IDOC types are created.
Normal flow:
MESSAGE TYPE-->IDOCTYPE, PROCESS CODE
IDOC TYPE --> SEGEMENT TYPES
IDOC records are of three types. 1)Control Record holds the Sender/REceiver info, data header etc.,
2) Data record holds the data or body of message
3) Status record to hold the message status pre and post transmission.
All these makes a full cycle and is not an easy job to do buddy.
I am sure, nobody would want to create these in XI.
Let us all know what you were trying to achieve.
Good Luck,
Srini.

BI Idoc Type IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE

Hi all,
how can we solve the IDoc miss match in source system (ECC6).
Error :
BI Idoc Type ZSTC029 IS NOT THE SAME AS SOURCE SYSTEM IDOC TYPE ZSTC031
please provide me solutions..
Thanks in advance,
Venkatesh

Hi Venkatesh,
Check here.........
BW idoc type not same as source system idoc type
Thanks,
Vijay.

EDI: Syntax error in IDoc (mandatory group/segment missing)

hi EDI/IDoc experts,
Need you help urgently. According to the requirement, i need populate a segement E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
E1IDT01 was populated, but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
EDI: Syntax error in IDoc (mandatory group missing)
Message no. E0079
Diagnosis
The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
Procedure
Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

Hi all,
Thanks so much for your concern!
Finally ,this problem has been figured out .
Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because I didn't fill data correctly. I missed to keep SY-TABIX in momory .
when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX is changed .So we can't just use MODIFY EDIDD_TABLE INDEX SY-TABIX in the last . we should define a local variable to keep SY-TABIX in memory and then use it to modify EDIDD_TABLE.
Follow is the final code.
IF SEGMENT_NAME = 'E1IDT01'.
TABLES :STXL.
* Define for long text getting
DATA: LIT_TLINE LIKE TLINE   OCCURS 0 WITH HEADER LINE.
DATA: LV_STRING(2000) TYPE C.
DATA: LV_TDNAME TYPE THEAD-TDNAME,
        LV_ID     TYPE THEAD-TDID     VALUE '0001',
        LV_LANG   TYPE THEAD-TDSPRAS VALUE 'E' ,
        LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
data:   LV_LINE   TYPE I,                " long Text lines
        LV_LEN    TYPE I,                " long Text length
        LV_TABIX LIKE SY-TABIX.
* Clear memory
CLEAR:LV_TDNAME,
        LV_STRING,
        LV_LINE,
        LIT_TLINE, LIT_TLINE[],
        LV_LEN,
        LV_TABIX.
* Keep sy-tabix memory using a variable--This is the key point
LV_TABIX = SY-TABIX.
* Combine TDNAME with company code + accounting doc + fiscal year + item number.
    CONCATENATE REGUP_DATA-BUKRS REGUP_DATA-BELNR
                 REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO LV_TDNAME.
* When vendor item has long text , read long text into lv_string
    SELECT SINGLE *
      FROM STXL
      WHERE TDOBJECT = LV_OBJ
        AND TDNAME   = LV_TDNAME
        AND TDID     = LV_ID
        AND TDSPRAS = 'E'.
    IF SY-SUBRC = 0.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT   = SY-MANDT
          ID       = LV_ID
          LANGUAGE = LV_LANG
          NAME     = LV_TDNAME
          OBJECT   = LV_OBJ
        TABLES
          LINES    = LIT_TLINE.
      IF NOT LIT_TLINE[] IS INITIAL.
        DESCRIBE TABLE LIT_TLINE LINES LV_LINE.
        DO LV_LINE TIMES.
          READ TABLE LIT_TLINE INDEX SY-INDEX.
          CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
        ENDDO.
        LV_LEN = STRLEN( LV_STRING ).
* Make sure we only need less than 840 charicters
        IF LV_LEN > 840.
          LV_STRING = LV_STRING+0(840).
          LV_LEN    = 840.
        ENDIF.
* Populate Vendor item long text with segment E1IDT01 start from
* Fields TXT03 to TXT14.
         EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
        MODIFY EDIDD_TABLE INDEX LV_TABIX.
      ENDIF.
    ENDIF.
ENDIF.

Message type SHPCON, idoc type DELVRY01

Hi SAP Gurus,
I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
I tried to simulate the inbound entry via WE19. I was not able to proceed with the posting because I encountered error 51 in idoc.
Field EXIDV empty
Field VHILM empty
These fields are in E1EDL37 and E1EDL44 respectively, and referring to HU information in which we don't have.
What I have filled up are the fields:
E1EDL20-VBELN = DO num
E1EDL20-VSTEL = Plant
E1EDL18-QUALF = "PGI"
E1ADRM1-PARTNER_Q = "WE"
E1ADRM1-PARTNER_IQ = recv plant
E1EDTH13-QUALF = "015"
E1EDTH13-NTANF = date today
E1EDL24-POSNR = 000010
E1EDL24-MATNR = material num
E1EDL24-WERKS = delv plant
E1EDL24-LGORT = sloc
E1EDL24-LFIMG = quantity
E1EDL24-VRKME = unit
E1EDL24-LGMNG = quantity
E1EDL24-MEINS = unit
May I know how to avoid this or if I missed some fields that resulted to this error ? Or am I using the wrong message type?

Hari,
I can definitely use WE19 to reprocess it. However my problem is the source of this information. If we implement this process, we would not know where to get this information since we don't use handling units. To add to this, the field VHILM that the system is asking is "packaging material" which we don't use and don;t have.
How to get rid of these fields? In VL02N, there is no handling units when I click on the pack icon. Only the material and the quantity.
Thanks.

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.

IDOC Type - TRXSTA01 is missing in 4.6 C

Similar Messages

Maybe you are looking for