Extended idoc not populating(urgent)

hi guys
i have extended the basic idoc type delvry03 and created an extension delvrtext for it.however when i trigger the idoc from an output type the extended segments are not populated.is there a way you can put a break point in the code.if that is possible it will help me a lot.i am using the FM idoc_output_delvry to create this.i tried putting break points in rsnasted as well as the above FM but it doesnt stop and the idoc gets created.please tell me how do i make sure my code for populating the extended segments is running properly.
please reply as soon as possible.thanks for your time and help.

hi guys.
thanks for the reply first of all.srinivas what do u mean by assign the extension to application object?i have done the configuration in we82 where i have attached the basic idoc type and extension to message type desadv. the function module is attached to the process code which is used in partner profiles for the idoc processing.can u explain me in detail.the idoc standard idoc is getting created but not the extended segments.also there is this weird message when i run a check on the partner profiles as follows
 Entry XIDCLNT300/LS/LS/DESADV /
 Message Control entry exists for this entry
 Port exists
 Basic type exists
 Extension exists
 Combination of basic type and extension is not possible
 Link exists between logical message and IDoc type
what does this mean any idea?
once this check is done probably i can go and do the breakpoints.i just have a feeling that i am missing some small thing here.
please let me know
thanks

Similar Messages

ZBATMAS03 - extended idoc segment population

Hi,
I've found an extended IDoc ZBATMAS03 (basic type: BATMAS03). It's being used for generating outbound IDOc usiong change pointers. A new segment Z1BATMAS has been added to the extended one.
Now I'm not able to find where this segment is being populated.
I tried searching in FM: MASTERIDOC_CREATE_SMD_BATMAS and the where used list for the new segment.
can anyone tell me how to find where the above new segment is being populated?
regards,
Ravi

Hi,
First up all the FM name is MASTERIDOC_CREATE_SMD_BATMAS, I surprised after dont find any exit for this FM.. May be you need to copy this FM and do the changes... Yes this the FM used to create an Idoc BATMAS.
You need to create custom function module with reference to standard FM, fill your extension segment.
Regards,
Suresh.D

Idocs not populating the fields

Hi
We are using Extended Classic Scenario. After the shopping cart is approved, the PO is generated in the backend R/3. The PO is generated in the backend and the idoc is triggered which is sent to supplier.
The problem we are facing is as below:
There are some fields in the idocs which are not getting populated. We are using badi implementation BBP_PO_INBOUND_BADI in the backend. We have used both the methods BBP_MAP_BEFORE_BAPI
BBP_MAP_AFTER_BAPI
The table EKPO is getting updated but the idoc does not have the fields.
Also when we are second time retriggering the output the idoc is having the required fields.
Kindly advice.
Thanks and Regards
Manoj

Hello,
It looks the first generation occurs to early in the process.
Can you should check the processing time you defined in condition records ?
3 is too early, 4 should work because a commit work is done before. And at worst set it to 1 (selection report) and schedule a job to process the message.
Rgds,
Pierre

Problem about extended IDOC(urgent)

Hi experts,
i have idoctype,extended idoc,and one include.. i need modify that according to the requirement.. here i will give the idoctype and extended idoc type and include program .. please help me where exactly i need to do the change and what are the steps required for the requirement..
Exact Requirement: Modify the program which populates the idoctype invoice02 and extension zinvoice02 , if netvalue is zero(vbrp-netwr = 0) then populate the idoc segment E1EDP01.E1EDP26 , BETRG WITH QUALF = # 011' WITH ZERO VALUE. curently segment is not populated.
Please help me in this and explain the steps required for this.
idoctype:invoice02
extended idoc:zinvoice02
include:ZXEDFU02
 Here i am giving the include program
CASE dobject-kschl.
WHEN 'ZGRI' OR 'ZGDF' OR 'ZGRN' OR 'ZGAE'.
 t_int_edidd[] = int_edidd[].
 t_xtvbdpr[] = xtvbdpr[].
 ta_xvbdkr = xvbdkr.
 CASE int_edidd-segnam.
 WHEN 'E1EDK01'.
 ta_e1edk01 = int_edidd-sdata.
 PERFORM get_shipment_data.
 PERFORM get_route_data.
 int_edidd[] = t_int_edidd[].
 WHEN 'E1EDP01'.
Update segment E1EDP01
1. Update field E1EDP01-PSTYP
2. Accumulated net weight & quantity of batch split items against
E1EDP01 segment of the main invoice item.
 ta_e1edp01 = int_edidd-sdata.
 i_tabix = sy-tabix.
 CLEAR: ta_e1edp02. "DIAG01+
 PERFORM update_segment_e1edp01.
 MOVE ta_e1edp01 TO t_int_edidd-sdata.
 MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
Populate segment Z1EDP08
Fields: ZZDESPACTY_A, ZZACTYUOM
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDP08'
 CHANGING n_subrc.
 CHECK n_subrc EQ 0.
 PERFORM calc_invoice_item_zzdespacty_a. "DIAG02+
 int_edidd[] = t_int_edidd[]. "DIAG02+
 WHEN 'E1EDP02'. "DIAG01+
 IF int_edidd-sdata(3) = '016'. "DIAG01+
 ta_e1edp02 = int_edidd-sdata. "DIAG01+
 ENDIF. "DIAG01+
 WHEN 'E1EDP19'.
Populate segment Z1EDL24
Fields: Material Characteristics or Material Class '001'.
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDL24'
 CHANGING n_subrc.
 IF n_subrc EQ 0.
 ta_e1edp19 = int_edidd-sdata.
 CASE ta_e1edp19-qualf.
 WHEN '002'.
 PERFORM get_mat_characteristic USING ta_e1edp19-idtnr.
 PERFORM fill_segment_z1edl24.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
 ENDIF.
 WHEN 'E1EDP26'.
Populate segment E1EDP26
Fields: BETRG
 i_tabix = sy-tabix.
 ta_e1edp26 = int_edidd-sdata.
 IF ta_e1edp26-qualf = '001'. "Gross Price which is always present
 PERFORM fill_segment_e1edp26.
 int_edidd[] = t_int_edidd[].
 ENDIF.
 WHEN 'E1EDP08'.
Populate Segment Z1EDL37 *
Fields: Bespoke fields from Handling Unit (VEKP)
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDL37'
 CHANGING n_subrc.
 CHECK n_subrc EQ 0.
 ta_e1edp08 = int_edidd-sdata.
 PERFORM fill_segment_z1edl37.
Populate Segment Z1EDP08 *
Fields: Total Despatch Activity *
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDP08'
 CHANGING n_subrc.
 CHECK n_subrc EQ 0.
 PERFORM calc_invoice_item_acty_total.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
WHEN 'ZGDW'.
Line above added line below removed - Assyst 73789
WHEN 'ZGIN'.
 t_int_edidd[] = int_edidd[].
 t_xtvbdpr[] = xtvbdpr[].
 ta_xvbdkr = xvbdkr.
 CASE int_edidd-segnam.
Start SU02
 WHEN 'E1EDK01'.
 ta_e1edk01 = int_edidd-sdata.
 i_tabix = sy-tabix.
Get the conversion factor
 PERFORM modify_exchange_rate.
 MOVE ta_e1edk01 TO t_int_edidd-sdata.
 MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
 int_edidd[] = t_int_edidd[].
End SU02
*************************************************************SAM01 START
 WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
 ta_e1edp02 = int_edidd-sdata.
 CASE ta_e1edp02-qualf.
 WHEN '002'.
 PERFORM fill_segment_z1edp02.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDP02'
 ta_z1edp02.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
***************************************************************SAM01 END
 ENDCASE.
Start of JvdM01
WHEN 'ZGII'. "JvdM01
 t_int_edidd[] = int_edidd[].
 t_xtvbdpr[] = xtvbdpr[].
 ta_xvbdkr = xvbdkr.
 CASE int_edidd-segnam.
 WHEN 'E1EDK01'.
Populate segment Z1EDKSH and Z1REM_STE_CDE
Fields: Shipment Number for Invoice
 Reason code for sales order
 ta_e1edk01 = int_edidd-sdata.
 PERFORM fill_segment_z1edksh_ds.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDKSH'
 ta_z1edksh.
 PERFORM fill_segment_z1rem_ste_cde.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1REM_STE_CDE'
 ta_z1rem_ste_cde.
 int_edidd[] = t_int_edidd[].
 WHEN 'E1EDKA1'.
Populate segment Z1EDKA1
Fields: Customer Account Group
 ta_e1edka1 = int_edidd-sdata.
 CASE ta_e1edka1-parvw.
 WHEN 'RE'. "Bill To Party
 PERFORM fill_segment_z1edka1.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDKA1'
 ta_Z1EDKA1.
 int_edidd[] = t_int_edidd[].
 ENDCASE.
 WHEN 'E1EDP01'.
Read segment E1EDP01 for use later "JVDM02
 ta_e1edp01 = int_edidd-sdata.
 WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
 ta_e1edp02 = int_edidd-sdata.
 CASE ta_e1edp02-qualf.
 WHEN '002'.
 PERFORM fill_segment_z1edp02.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDP02'
 ta_z1edp02.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
 WHEN 'E1EDP19'.
Populate segment Z1EDL24 and Z1EDP01 "JVDM02
Fields: Pack Size Activity for Material
 Total Activity for Invoice Item
 ta_e1edp19 = int_edidd-sdata.
 CASE ta_e1edp19-qualf.
 WHEN '002'.
 PERFORM fill_segm_z1edl24_and_z1edp01.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDL24'
 ta_z1edl24.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDP01'
 ta_z1edp01.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
 ENDCASE.
End JvdM01
ENDCASE.
Start SU02 Code Comment for implementing IR 340
**mpc01 - start of insert
start assyst 73789
*IF dobject-kschl = 'ZGDW'."amersham invoices
**IF dobject-kschl = 'ZGIN'."amersham invoices
end assyst 73789
CASE int_edidd-segnam.
for the organisation data header
 WHEN 'E1EDK14'.
 MOVE int_edidd-sdata TO ta_e2edk14.
 where is qualifying organisation = 003 (delivering company code).
 IF ta_e2edk14-qualf = '003' AND ta_e2edk14-orgid NE space.
 SELECT SINGLE waers
 INTO t001-waers
 FROM t001
 WHERE bukrs = ta_e2edk14-orgid.
 IF sy-subrc = 0.
 t_int_edidd[] = int_edidd[].
 get the billing date for the invoice
 LOOP AT t_int_edidd WHERE segnam = 'E1EDK02'.
 MOVE t_int_edidd-sdata TO ta_e1edk02.
 IF ta_e1edk02-qualf = '009'."billing date
 w_fkdat = ta_e1edk02-datum.
 EXIT.
 ENDIF.
 ENDLOOP.
 if no invoice date use current date
 IF w_fkdat IS INITIAL.
 w_fkdat = sy-datum.
 ENDIF.
 change the general document header
 LOOP AT t_int_edidd WHERE segnam = 'E1EDK01'.
 i_tabix = sy-tabix.
 MOVE t_int_edidd-sdata TO ta_e1edk01.
 set the field to the default currency code for the company
 ta_e1edk01-hwaer = t001-waers.
 if the default value equals the idoc currency then exit
 IF t001-waers = ta_e1edk01-curcy.
 EXIT.
 ENDIF.
 get the exchange rates
 SELECT *
 INTO TABLE t_tcurr
 FROM tcurr
 WHERE kurst = 'NYB1' " SU01
 WHERE KURST = 'GEBU' " SU01
 AND fcurr = ta_e1edk01-curcy
 AND tcurr = t001-waers.
 IF sy-subrc NE 0."no values found
 error the idoc
 MESSAGE e400(vf) WITH c_exchange_rate_error
 RAISING error_message_received.
 EXIT.
 ENDIF.
 LOOP AT t_tcurr.
 convert to date from inverted date to normal date format.
 CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
 EXPORTING
 input = t_tcurr-gdatu
 IMPORTING
 output = w_datum.
 CONCATENATE w_datum+6(4)
 w_datum+3(2)
 w_datum(2)
 INTO t_tcurr-datum.
 MODIFY t_tcurr.
 ENDLOOP.
 sort the exchange rates with the newest first.
 SORT t_tcurr BY datum DESCENDING.
 read the first value in the table ie the newest.
 LOOP AT t_tcurr WHERE datum <= w_fkdat.
 EXIT.
 ENDLOOP.
 IF sy-subrc NE 0."no values found
 error the idoc
 MESSAGE e400(vf) WITH c_exchange_rate_error
 RAISING error_message_received.
 EXIT.
 ENDIF.
Start SU01
Get the Exchange rate from the function module and populate
E1EDK01 TABLE
 w_fcurr = ta_e1edk01-curcy.
 call function 'CONVERT_TO_LOCAL_CURRENCY'
 exporting
 date = w_fkdat
 foreign_amount = '0'
 foreign_currency = w_fcurr
 local_currency = t001-waers
 type_of_rate = 'GEBU'
 importing
 exchange_rate = t_tcurr-ukurs
 exceptions
 no_rate_found = 1
 overflow = 2
 no_factors_found = 3
 no_spread_found = 4
 derived_2_times = 5
 others = 6.
End SU01
 ta_e1edk01-wkurs = t_tcurr-ukurs.
 change the header data in segment
 MOVE ta_e1edk01 TO t_int_edidd-sdata.
 update the current idoc segment
 MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
 EXIT.
 ENDLOOP.
 update all of the idoc segments
 int_edidd[] = t_int_edidd[].
 ENDIF.
 ENDIF.
ENDCASE.
*ENDIF.
**mpc01 - end of insert
End SU02 Code Comment for implementing IR 340

Hi Venu,
Try with this code.
If vbrp-netwr = 0.
 WHEN 'E1EDP26.
CASE ta_e1edp26-qualf.
ta_e1edp26 = int_edidd-sdata.
WHEN '011'.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'e1edp26'
ta_e1edp26.
int_edidd[] = t_int_edidd[].
ENDCASE.
ENDIF.
Thanks
Manju.

Ship to party not populating in segment in whsord idoc

HI,
we are creating two delivery with ship to party as 52004 and 56003 (two different sales orders with differnt sold to ). the deliveries are trigerring outbound whsord idoc. The issue is in the segment E1ADRM1 segment for WE qualifier , in the field, " Partner_id", the ship to party 52004 and 56003 is not populated. Rather a constant value 32500000789 is populated in "partner_id " field in both deliveries
Our Abaper is not willing to identiy the same since it is s standard idoc.
Pls can you help as to w hy ship to 52004 and 56003 is missing in partner_id field and some other value 32500000789 is coming ? all other deliveries are created ok.
rgds
Pamela

Hi Pamela,
can you Please share some more information like IDoc details. so that v can analyze more.
Regards,
VSN

Message type is not populating in the Inbound idoc control record

Hi,
I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
The settings which I have done in WEDI as follows:
1. Created Idoc segments with necessary fields and released
2. Created Idoc type for the segment type
3. Created message type
4. Assigned message type to basic type
5. In the inbound processing settings,
filled the ALE attributes with the Idoc function module name and input value '0'
6. Assigned FM to basic type and message type
7. Created process code and assigned the process code to message type
Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
Best Regards,
Mallika

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

Data not populating in my idoc

Hi guru,
i am writting these below code .
please look my code.here date i am moving from : move W_datum1 to int_edidd-sdata.
so in debugging mode i am getting date value in int_edidd-sdata.
but why the value is not populating in my segment of idoc.can u tell me where is the probleam in my code???
If XVBDKR-VKORG = 'EDM1'
*CONTROL_RECORD_OUT-STDMES = 'INVOIC'
AND DOBJECT-KSCHL = 'ZEDI'.
if INT_EDIDD-SEGNAM = 'E1EDK02'.
LOOP AT INT_EDIDD WHERE SEGNAM = 'E1EDK02'.
            E1EDK02 = INT_EDIDD-SDATA.
            IF E1EDK02-QUALF = '009'.
            W_datum2 = E1EDK02-datum.
            ELSEIF E1EDK02-QUALF = '012'.
              W_datum1 = E1EDK02-datum.
            ENDIF.
          ENDLOOP.
endif.
IF W_datum1 GT W_datum2.
          W_datum1 = W_datum2.
    move W_datum1 to int_edidd-sdata.
MODIFY int_edidd INDEX hilfe_tabix.
          EXIT.
         ENDIF.
       ENDIF.

hi,
my current code is below...
please help
If XVBDKR-VKORG = 'EDM1' and
CONTROL_RECORD_OUT-MESTYP = 'INVOIC'
AND DOBJECT-KSCHL = 'ZEDI'.
if INT_EDIDD-SEGNAM = 'E1EDK02'.
MOVE int_edidd-sdata TO e1edk02.
loop at INT_EDIDD where SEGNAM = 'E1EDK02'.
            E1EDK02 = INT_EDIDD-SDATA.
            IF E1EDK02-QUALF = '009'.
            W_datum2 = E1EDK02-datum.
            ELSEIF E1EDK02-QUALF = '012'.
              W_datum1 = E1EDK02-datum.
            ENDIF.
          ENDLOOP.
endif.
IF W_datum1 GT W_datum2.
          W_datum1 = W_datum2.
W_E1EDK02-DATUM = W_datum1.
int_edidd-segnam = 'E1EDK02'.
move W_E1EDK02-datum to int_edidd-sdata.
APPEND int_edidd.
    MODIFY int_edidd INDEX hilfe_tabix
   lv_flag = 'X'.
          CLEAR: W_datum1,W_datum2.
          EXIT.
         ENDIF.
       ENDIF.

Prob in extended idoc - ORDER05

Hi,
I have extended basic type orders05. when i run the FM, EXIT_SAPLVEDC_003, inside where i have written code for populating the z segments, i am unable to see the segments at all.
i mean, i can NOT see edidd-segnam EQ extended segment names. i have created a project in Cmod and its active as well.
Please help me out.
Edited by: Aafaque Husain on Dec 21, 2007 10:29 AM

Thanks Martin,
I am able to see the extended idoc segments now as per logic told by you, but now when i m testing the idoc and checking the result in we02, i m getting an error which reads as follows,
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZST_STORMS does not occur at the current level of the basic type ORDERS05 (extension ZORDER05).
This error can have several reasons:
The segment ZST_STORMS is assigned to a group whose header segment does not occur.
The segment ZST_STORMS does not exist in the syntax description of the basic type ORDERS05 (extension ZORDER05).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ZORDER05).
please can u help me out in this.
Thanks for ur help extended.

Message attachment with Extended IDOC

Hi,
I have created one extension of idoc type debmas04 as ZKNA1 .I have attached the message debmas with idoc type debmas04 with extension Z1KNA1 with release 620.
when I am running bd12 the extended part is not populating.
How it can be done ?
Thanks,
               sanjukta

Hi,
When ever you send the information thro' BD12 it calls the FM MASTERIDOC_CREATE_REQ_DEBMAS inside which there is a call to another function module MASTERIDOC_CREATE_DEBMAS.
In the function module MASTERIDOC_CREATE_DEBMAS
* Customer exit
    call customer-function '001'
         exporting
              message_type = message_type
              idoc_type    = c_idoctp_debmas
              segment_name = c_segnam_e1kna1m
         importing
              idoc_cimtype = idoc_cimtype
         tables
              idoc_data    = t_idoc_data.
Which takes you to exit EXIT_SAPLVV01_001. You can find include zxvsvu01, where you can populate the additional information about new z-segment.

Extend idoc

for extended idoc i added the extended segment to basic type and doen
the code as per that but i would like to confirm one thing that for
every extended idoc for process code we need to modify the existing FM
like MASTERIDOC_CREATE_DEBMAS ,
for this FM we need to finc the enhansment and then modify the code
as per that , so is the same for all extended idoc we need to find
related FM for that and find enhancement and modify .

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
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.
regards,
srinivas

S_Tcode not populating in simulation

Hello-
When running a simulation in CC 5.2, and using permission level analysis, you have to manually add s_tcode in the object table.
Steps:
Insert a role, press simulation, add an action, click on the objects button; s_tcode is not populated. When it is not added, it is not causing any conflicts, which is incorrect. In an older version of CC 4.0, before a support pack was installed, this problem was evident. Is it a product-level issue with CC 5.2? If so, how do you work-around it?
This is an urgent issue, since we have to run simulations almost everyday, as we have not implemented Risk Terminator. Thanks!...
Noah
Edited by: Noah Phillip on Feb 26, 2008 7:51 PM

Ibrahim-
Yes, I understand, but not inserting s_tcode in the object manually produces wrong results after executing the simulation. Inserting s_tcode manually produces the correct results.
The same issue was evident in CC 4.0, until SAP produced a patch for it. I am wondering if they overlooked this patch while developing CC 5.2...
Noah

Profit center not populated in SO

Hi CRM experts,
We have a typical issue when a SO is replicated from CRM (SAP CRM 7) into ECC 6.0, its not populating the proit center into the field in account assignment tab at item level. When the SO is created within ECC using VA01 with exactly the same data, it populates profit center correctly. Any ideas / help is appreciated.
Thanks in advance,
Gopal Turaga

Hi
You need to check the following:
1. The cost center settings in T Code ACSET
2. The splitting characteristics in the menu path:
IMG>Financial Accounting (New)>General Ledger Accounting(New)>Business Transactions>Document Splitting>Extended Document Splitting
3. If cost center is a required field in your asset master and if you have assigned a cost center in the asset master
4. If a profit center has been assigned in the cost center master assigned in your asset master.
Thanks & Regards
Sanil K Bhandari

Profit Center not populated in Asset Transactions

Hi
We are trying to post asset transactions. We are on ECC 6.0 with New GL and document splitting on profit Center. while posting the periodic depreciation, system is not allowing posting of the document, saying that profit center is not populating in the line item. Pls suggest.
Regards
Rupal

Hi
You need to check the following:
1. The cost center settings in T Code ACSET
2. The splitting characteristics in the menu path:
IMG>Financial Accounting (New)>General Ledger Accounting(New)>Business Transactions>Document Splitting>Extended Document Splitting
3. If cost center is a required field in your asset master and if you have assigned a cost center in the asset master
4. If a profit center has been assigned in the cost center master assigned in your asset master.
Thanks & Regards
Sanil K Bhandari

Problem in Extended Idoc

Hi All,
I have Extended ORDERS05 for adding custom fields for inbound process,
Steps i have fallowed to create Extend Idoc:
1,Created new segment with all Z-fields and released,
2,Created Extension Idoc with reference standard Idoc ORDER05, and added custom segment under standard segment E1EDP01,
released Extend Idoc,
am able to see all Z-fields in Z-segment,
but my problem is am unable to see any standard fields under any standard segment in my Extended Idoc?
why am not able to see all standard fileds?
Regards
suresh.d

Hi,
Are you checking in WE30 or in WE02?
In WE30 you cans ee only Segment names.
Give the segment name in SE11 and then see if you are able to see the fields.
Regards,
Sravan

Problem creating extended IDOC

Hi Experts,
I am currently working on CRM 5.0. I need to create segment and attach it to the standard basic IDOC type CRMXIF_PARTNER_SAVE01. I am able to create segment in WE31 but i am unable to add that to the basic standard IDOC type.
It is displaying message "Action is not possible for generated idoc types".
Is there any other way to add this segment to the standard IDOC.
It will be great help if u can send me some documents on this...
Thanks,
Samm

Hi,
Create Extended IDOCe using transaction WE30.
-If u want to extend idoc type which already exists then use the radio button extension(where we can add few new fields
-After this click on create button as described above. It takes you to a popup screen where you fill the description and also select the radio button accordingly and say ok
-we go to next screen select idoc type and click on create new It gives a pop up window
-Once you are done with the addition save the IDOC type and release the idoc type
Goto-> Edit -> Set release.
This completes the creation of Ext IDOC type.
- Then assign this extension to the IDoc type in WE82.
Reward with points if helpful.
Regards,
Vijay

Extended idoc not populating(urgent)

Similar Messages

Maybe you are looking for