Field Name in IDOC is missing

Hi to All,
I created a sample program for outbound IDOC creation with one segment (contains two fields). When I populate the value in those fields, then IDOC created successfully with two fields. When the value is INITIAL to any fields then those field name is not displaying in the IDOC. But I want to display the field name even if its value is INITIAL.
Can anyone suggest solution for this issue?
Thanks in Advance,
Regards,
Raghu

Hi rajesh
i have created a test file by taking the idoc structure and then i am trying to test the scenario by placing the file in the Integartion Engine.
The data which i have given for 3 segements(Header,Detail,Footer), the header dat and the footer data are coming out fine in we05. But for the detail segement i am giving values for 6 fields, only 2 filelds values are being displayed in weo5, remaining data is not being shown.
In the sxmb_moni the status of the message is sucessful.It is shwoing sucess flag.
Thank you

Similar Messages

Need billing text field name for IDoc mapping

Hi Friends,
our users use CRM web application to send orders to SAP via IDocs. They want to have billing text (In German it is called Rechnungstext or Faktura text) so that they can enter some text here if they want to enter something. My question is, what is the field name and IDoc segment for billing text? We need this information to map in XI.
Br, Sats.

The solution is:
The standard Idoc text segment can be used for the text in sales order. From SD side the text types have to be customized. This is necessary for the XI mapping.
Regards,
Sats.

Field names Missing in the (Excel) Mail attachment

Hi ,
I am trying to send my ALV Grid Output as Excel Email attachment using the below code
The problem is that the field names are missing in the receivers Mail.
i.e
*Name*   *Emp Code*   * Branch*         "this is missing
abc         123                 ukp
I searched many threads but unable to find the solution for this.
Kindly suggest me regarding this issue.
loop at p_eadd.
    if p_eadd-low <> space.
      clear reclist.
      reclist-rec_type = 'U'. "Internet-adress
      reclist-receiver = p_eadd-low.
      reclist-express = 'X'.
      append reclist.
    endif.
endloop.
* endif.
* Send the document
call function 'SO_NEW_DOCUMENT_SEND_API1'
     exporting
          document_type              = 'RAW'
          document_data              = doc_chng
*         PUT_IN_OUTBOX              = 'X'
     tables
          object_content             = objcont
          receivers                  = reclist
     exceptions
          too_many_receivers         = 1
          document_not_sent          = 2
          operation_no_authorization = 4
          others                     = 99.
ld_aplstat = '4'.
case sy-subrc.
    when 0.
      loop at reclist.
        if reclist-receiver = space.
          name = reclist-rec_id.
        else.
          name = reclist-receiver.
        endif.
        if reclist-retrn_code = 0.
          write: / name, ': succesfully sent'.
        else.
          write: / name, ': error occured'.
        endif.
      endloop.
      ld_aplstat = '0'.
    when 1.
      write: / 'Too many receivers specified !'.
    when 2.
      write: / 'No receiver got the document !'.
    when 4.
      write: / 'Missing send authority !'.
    when others.
      write: / 'Unexpected error occured !'.
endcase.
*.Tell workflow to go on
clear ls_scma_event.
ls_scma_event-wf_event = cs_wf_events-finished.
ls_scma_event-wf_witem = wf_witem.
ls_scma_event-wf_okey = wf_okey.
call function 'KPEP_MONI_CLOSE_RECORD'
    exporting
      ls_key        = gs_key
      ls_scma_event = ls_scma_event
    changing
      ld_aplstat    = ld_aplstat
    exceptions
      no_id_given   = 1
      others        = 2.
call function 'SAP_CONVERT_TO_XLS_FORMAT'
      exporting
       i_field_seperator          = ' '
       i_line_header              = 'X'
        i_filename                 = p_file
*   I_APPL_KEEP                = ' '
      tables
        i_tab_sap_data             = it_final
* CHANGING
*   I_TAB_CONVERTED_DATA       =
     exceptions
       conversion_failed          = 1
*   OTHERS                     = 2
    if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
Thanks in Advance,
Mr. Ben

Hi Ben,
Follow the code below....
Your internal table it_final will have the attachment data. After you got the attachment data do the following
gc_ret TYPE c VALUE cl_abap_char_utilities=>cr_lf.
lt_attachment        TYPE TABLE OF solisti1 ,
gt_attach TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0 WITH HEADER LINE,
CLEAR:gs_attach.                      <this will have your attachment, declare a structure which contains fields of your excel sheet>
<before this you have to copy all the fields from your final internal table which should be attached to email to gs_attach>
For attaching field names
    CONCATENATE gc_ret gs_attach INTO gs_attach.
    gs_attach = gs_attach+1.
    APPEND gs_attach TO gt_attach.
CLEAR:lt_attachment.
      lt_attachment[] = gt_attach[].
SORT lt_attachment .
      DELETE ADJACENT DUPLICATES FROM lt_attachment COMPARING ALL FIELDS.
      CLEAR gs_attach.
      CONCATENATE <field names >
      INTO gs_attach SEPARATED BY gc_tab.
      INSERT gs_attach INTO lt_attachment INDEX 1.
<field addition ends>
call function 'SO_NEW_DOCUMENT_SEND_API1'
     exporting
          document_type              = 'RAW'
          document_data              = doc_chng
        PUT_IN_OUTBOX              = 'X'
     tables
          object_content             = objcont
          receivers                  = reclist
        contents_bin               = lt_attachment
     exceptions
          too_many_receivers         = 1
          document_not_sent          = 2
          operation_no_authorization = 4
    if sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
Regards,
Aravind.

IDoc: E1EDL44 2 contains different field names in segments

Our client picks up delivery data sent over EDI and a Middleware program to put it in a form.
The Middleware picks up the customer material number from KDMAT of the HU data.
For 1 particular material X KDMAT is not available in the idoc record E1EDL44 2.
With not available I mean KDMAT is not in the list of field names.
This leads to inconsistencies on our client's form for which we are penalized.
For material Y in the same record E1EDL44 2 (different segment) KDMAT is available.
This one is populating correctly on the client's form.
I checked VD52 for material X and there exist an entry for KDMAT.
What more do I need to analyze?
How do I solve this issue?
Best regards,
Geert

Hi,
Are you talking about an outbound interface or inbound interface.
If it is an outbound interface, if the Customer Material number is maintained in VD52 transaction then it would automatically come into the IDOC, if it is not coming then check the FM and the corresponding user exit, some custom code would have cleared that value in the idoc segment.
Thanks,
Mahesh.

Throws sqlError: Field Name Missing

select
decode(instr('Americas', 'United States'),0,'',decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('Americas', 'United States'),0,'',decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('Asia', 'Europe'),0,'',decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('Asia', 'Europe'),0,'', decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('United States', 'Americas'),0,'',decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('United States', 'Americas'),0,'', decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('Europe', 'Asia'),0,'', decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]')),
decode(instr('Europe', 'Asia'),0,'', decode('Unix', 'Unix', '[email protected]', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', '[email protected]', 'Linux', '[email protected]'))
from dual
Throws sqlError: Field Name Missing
Plz help me.

Doesn't for me:
SQL> select
2 decode(instr('Americas', 'United States'),0,'',decode('Unix', 'Unix', 'tsoserverunixoperations@
ge.com', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', 'ts
[email protected]', 'Linux', '[email protected]')),
3 decode(instr('Americas', 'United States'),0,'',decode('Unix', 'Unix', 'tsoserverunixoperations@
ge.com', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', 'ts
[email protected]', 'Linux', '[email protected]')),
4 decode(instr('Asia', 'Europe'),0,'',decode('Unix', 'Unix', '[email protected]',
'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400'
, '[email protected]', 'Linux', '[email protected]')),
5 decode(instr('Asia', 'Europe'),0,'', decode('Unix', 'Unix', '[email protected]',
'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400
', '[email protected]', 'Linux', '[email protected]')),
6 decode(instr('United States', 'Americas'),0,'',decode('Unix', 'Unix', 'tsoserverunixoperations@
ge.com', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', 'ts
[email protected]', 'Linux', '[email protected]')),
7 decode(instr('United States', 'Americas'),0,'', decode('Unix', 'Unix', 'tsoserverunixoperations
@ge.com', 'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400', 't
[email protected]', 'Linux', '[email protected]')),
8 decode(instr('Europe', 'Asia'),0,'', decode('Unix', 'Unix', '[email protected]',
'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400
', '[email protected]', 'Linux', '[email protected]')),
9 decode(instr('Europe', 'Asia'),0,'', decode('Unix', 'Unix', '[email protected]',
'NT', '[email protected]', 'Mainframe', '[email protected]', 'AS400
', '[email protected]', 'Linux', '[email protected]'))
10 from dual
11 /
D D D D D D D D
- - - - - - - -Care to give a bit more info??????
Message was edited by:
david_tyler

Unable to get Field Names from Archived File

Hi All,
We have a ECC 6 Ehp4 system. When i retrieve Idocs archived using SARA, the data only contains application data. There is no field names available - eg: posting date, tax code etc. Please find below the background on this issue.
I configured archiving of process idocs (status 52,12,03) from EDIDC tables. I set up the settings for Archive Object IDOC and archived the data for 15 days.
Both archiving and deletion of data from the table was successful.
I tried reading the Idoc data from Archive File using the Information System option -> Info structure (available as default for Idoc).
But the data retrieved only shows the Application data for all the segments of the IDoc. The fields for the segments like Tax Code, Posting Date etc are not available in the data. Functional teams will not be able to make sense with just the application data.
Am I missing some setting? Is there any way to retrieve the related field values also ?
Please help.
Thanks and Regards,
Raghavan

Hi All,
There is tcode WE10. You could choose if the data source is archive and also the archive session. You will get the list of segments provided. click on the segment number and you will get the data.
Thanks and Regards,
Raghavan

How to find the field name of variable system information on SAP B1

Hi All,
I recently wanted to create a simple SQL query to list all ITEM MASTER DATE where the weight is blank. This is so i can get a list of all items with the weight information missing from the system to investigate.
It turns out the weight field within the SALES DATA tab is a system variable. When i pull the OITM table up within the query generator i can not identify where this variable name come up without guessing which can give me the wrong information.
Can someone point me into the direction on how to assisocate variable to a field name within SAP B1. This is also another problem if i wanted to display variable within Crystal report layout.
Regards

Hi Nick Dang,
Try This
SELECT T0.[ItemCode], T0.[ItemName], T0.[SalUnitMsr], T0.[SHeight1], T0.[SWidth1], T0.[SLength1], T0.[SVolume], T0.[SWeight1] FROM OITM T0 WHERE T0.[ItemCode] =[%0]
Thanks,
Srujal Patel

How to know where the value of a field in an IDoc is saved?

Hello SAPients!
I'm working in ECC 6.0. I have an Inbound Idoc of type WPUBON01. In the segment E1WPB01it has a field named BONNUMMER. My question is: How can I know what TABLE-FIELD is being populated with the value of that field? I mean, is there a way to know the mapping of the fields of an IDoc?
Thank you in advance for your kind help.

Hi,
The table name is WPLST
I did the following..
Go to the segement structure in SE12..
Double click on the data element for that corresponding field..
Then put a where used-list for that data element...To search in tables..
I got the table WPLST.
Thanks,
Naren

Flat file should have source field name and value

Hi Friends
I have a scenario of Idoc to Flat file , where in the target structure the field name and value should be present, generally only the value is available in a flat file.The target structure is as below:
for e.g RECTYPE is the Field Name and A is the value.
RECTYPE,A
DATEH,20111101
TIMEH,173125
RECTYPE,B
ORDNUM,4500054536
ORDITM,150
SUPDAT,20090218
PLNQTY,000000006
MATNR,14B300
BATCH,5697
PLANT,3026
DELIVTYPE,PO
SUPPLIER,0000023305
SUPNAME,Deutsche BP AG
SUPADRS,Erkelenzer Strasse 20
SUPCITY,Monchengladbach
SUPPOST,41179
SUPCOUN,DE
TRUCK_NBR,7589
BOND_FLG,X
STG_LOC,PLCL
LINE_ACTION,CRE
RECTYPE,B
ORDNUM,4500056721
ORDITM,10
SUPDAT,20090218
PLNQTY,000000013
MATNR,116703
BATCH,6589
PLANT,3026
DELIVTYPE,PO
SUPPLIER,0000023380
SUPNAME,DOW Belgium NV
SUPADRS,Havenlaan 7
SUPCITY,Tessenderlo
SUPPOST,3980
SUPCOUN,BE
TRUCK_NBR,7589
BOND_FLG,X
STG_LOC,PLCL
LINE_ACTION,CHG
RECTYPE,X
DATEH,20111101
TIMEH,173125
RECORDS,3

Hi,
     NameA.addHeaderLine
Specify whether the text file will have a header line with column names. The following values are permitted:
■       0 u2013 No header line
■       1 u2013 Header line with column names from the XML document
■       2 u2013 As for 1, followed by a blank line
■       3 u2013 Header line is stored as NameA.headerLine in the configuration and is applied
■       4 u2013 As for 3, followed by a blank line
This specification is only permitted if exactly one structure is defined.
regards,
ganesh.

Problem using alias field names in a sql query

Hello,
I have a question regarding a simple Oracle database SQL query writeup:
In the following (badly written but properly working) SQL query:
Query 1:
select
soe.field1,
(soe.field2 + soe.field3) as field4,
(soe.field5 - (soe.field2 + soe.field3)) as field6,
(select comp.parValue*soe.field7
from
CompTable comp) as parValue,
(select soe.field8 - (comp.parValue*soe.field7+ soe.field9)
from
CompTable comp) as field10
from
SomeTable soe
PROBLEM 1:
I am re writing the code (soe.field2 + soe.field3) to get the alias field4 or column name field4 that I have created on the fly in the previously for use with the following fields. Can't I rewrite the query as follows. There is something simple missing!
Query 2:
select
soe.field1,
(soe.field2 + soe.field3) as field4,
soe.field5 - field4 as field6, <<< field4 does not work here
(select
comp.parValue*soe.field7
from
CompTable comp) as parValue,
(select
soe.field8 - (comp.parValue*soe.field7+ soe.field9)
from
CompTable comp) as field10
from
SomeTable soe
PROBLEM 2:
Similar to the above problem, I was thinking to get a field parValue out of the CompTable table and re-use many times rather than the code shown in Query 1:
Query 3:
select
soe.field1,
(soe.field2 + soe.field3) as field4,
soe.field5 - field4 as field6,
soe.field7* (select comp.parValue from CompTable comp) as parValue1,
soe.field8 - (parValue1*soe.field7+ soe.field9) as field10 <<<< parvalue1 does not work here
parValue1*soe.field9 as TaxCondition <<<< parvalue1 does not work here
from
SomeTable soe
See that the query becomes so simple, but the above query does not work. There is something fundamentally wrong in my usage of the alias field names in creating other fields. The Query1 seems to be the only working option but its very slow as I am redoing and re-writing the whole code again and again to get the parValue field out of the CompTable table for use to create many other fields.
I will appreciate if you can guide me in the right direction on this issue.
Thanks and Regards
Rama

SELECT tmp.contract_no, tmp.Actual, tmp.Actual - tmp.NbHours
FROM ( SELECT t.contract_no, sum(l.hrs) AS Actual, (c.labour_hours * c.labour_progress_per) / 100 AS NbHours
FROM TASK_DELEGATION t
INNER JOIN COST_CODE c
ON t.cost_code = c.cost_code AND t.contract_no = c.contract_no AND t.is_inactive=0
INNER JOIN Labour.dbo.LABOURALLOT l
ON l.contractNo = c.contract_no AND l.costcode = c.cost_code AND l.pm = 'N'
GROUP BY t.contract_no, c.labour_hours, c.labour_progress_per
) tmp

Passing form field name to the subject line of the task assign email

Hello Everyone,
I am trying to create a process that need to pass one of the field data from a form to the task email assign but could not make it work right as expected. I think I miss something but could not figure it out myself. If any one has done this before, please share your knowledge.
Thanks in advance,
Han Dao

Hi Jasmin,
I thought it simple thing to do by passing the xPath to the subject line but for some reasons, it does not work instead it show the whole xpath on the subject line. Here is my xpath:
{$/process_data/FormData/object/data/xdp/datasets/data/FSFIELDS_/Form1936/EmpInfoSub/UserM gr$}
where Form1936 is the pageName, EmpInfoSub is sub-form, and UserMgr is field name on the form.
Thanks,
Han Dao

Field name not known   in old existing report.

We have a report that we have used for a long time and has always been fine. Today when we open it it says data will be lost because "Field name not known".   So you click ok and look at the report in design and the report is missing a bunch of fields. You look at the Field Explorer and it only shows the first field in the table. This report links 2 tables. The linking field is the first field in both tables.
I try to re-map datasource and no luck.   I close Crystal, open Crystal and create a new report, look at the same tables and all of the fields are there. Create similar report looking at same datasource, same tables, some of the same fields, and it works fine.
What is wrong with the original report and why won't it connect or show fields?

It may be that the report file became corrupted. Do you have a back up of that report anywhere? If not you could create a new report using the same tables and links and then have both new and old reports open and copy objects from the old report to the new report. Save it and then verify it all works as it should and replace the old report with then new report. Copy the old report somewhere safe also.
Thank you
Don

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
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.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

Authorization object to display table field names in english text in SE17

Hi,
One of users have issues with the filed name getting displayed in technical format instead of english text while browsing table information in SE17. Normally we can set this in through Settings->User Parameters. But here for this user, user parameter option is greyed out and he doesn't have access to SE16.
Is there any other way to change user specific parameters, instead of granting him accesss to SE16 or enabling user parameters in SE17?
Thanks,
Mano

Hi,
I made him run SU53 on SE17 transaction the log is showing that authorization check failed for S_ALV_LAYO with value 23.
Actually i have access SE16 and for me also, user parameter option is greyed out in SE17. I ran SU53 on SE17 in my session i also got same log.
One more observation is, the user's colleague also doesn't have access to SE16 and user parameter option is greyed out in SE17 but he can view the table field names in english. So we are wondering if some authorization object is missing here.
We do not want user to make any changes through GUI.
Thanks,
Mano.

Diferent key field names within a recordset

Hi
Can we have different key field names for records within a recordset.
When i give different key field names for Header and detail records in a recordset i get the error below: -
message not processed: com.sap.aii.messaging.adapter.trans.TransformException: Transformer Conversion3.0.5227 Error initializing Class: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found (4408) Parameter 'xml.keyFieldName' is missing (4403) ; nested exception caused by: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found (4408) Parameter 'xml.keyFieldName' is missing (4403)
Thanks

Hello Pratihchi,
One keyfield name is allowed, eventhough we have different records per recordset. Because we can differentiate the rows based on the keyfieldvalue and those value we need to mention in the fieldname. Check below link which contains the example on this.
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5393- [original link is broken] [original link is broken]> [original link is broken] File Adapter->Sender File Adapter for Content Conversion
Regards.
Prasanna.

Field Name in IDOC is missing

Similar Messages

Maybe you are looking for