How to create an RFC for MIGO transaction?

How to create an RFC for MIGO transaction?
I want my RFC to accept all details as accepted in MIGO transaction.
For the entered PO no, display the materials against it and allow user to enter the quantity for the same.
Then the user should be able to post the PO by executing the RFC.
Kindly revert asap.
Thanx in advance,
Bhakti

Put good movement header data in structure header
l_header-pstng_date = sy-datum.
l_header-doc_date = sy-datum.
l_header-ver_gr_gi_slip = space.
Assign goods movement code
l_wa_goodsmvt_code-gm_code = c_gm_code.
Add material, plant, and other line item details in
goods movement item table
l_wa_goodsmvt_item-material = l_wa_selected-matnr.
l_wa_goodsmvt_item-plant = l_wa_selected-werks.
l_wa_goodsmvt_item-stge_loc = l_wa_selected-lgort.
l_wa_goodsmvt_item-batch = l_wa_selected-charg.
l_wa_goodsmvt_item-move_type = l_wa_selected-mov_type.
l_wa_goodsmvt_item-entry_qnt = l_wa_selected-deviceid.
l_wa_goodsmvt_item-entry_uom = l_wa_selected-meins.
l_wa_goodsmvt_item-move_plant = l_wa_selected-zwerks.
l_wa_goodsmvt_item-move_stloc = l_wa_selected-zsloc.
l_wa_goodsmvt_item-move_batch = l_wa_selected-rec_batch.
l_wa_goodsmvt_item-serialno_auto_numberassignment = space.
APPEND l_wa_goodsmvt_item TO l_i_goodsmvt_item.
CLEAR l_wa_goodsmvt_item.
l_wa_serial_num-matdoc_itm = l_c_mat_doc_item.
l_wa_serial_num-serialno = l_wa_selected-sernr.
APPEND l_wa_serial_num TO l_i_serial_num.
CLEAR l_wa_serial_num.
To call BAPI BAPI_GOODSMVT_CREATE to transfer material of transfer
type one step
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
    EXPORTING
      goodsmvt_header       = l_header
      goodsmvt_code         = l_wa_goodsmvt_code
    IMPORTING
      goodsmvt_headret      = l_goodsmvt_headret
    TABLES
      goodsmvt_item         = l_i_goodsmvt_item
      goodsmvt_serialnumber = l_i_serial_num
      return                = l_i_return.
cheers
Aveek

Similar Messages

How to create user exit for MIGO check "item OK" Field select/unselect?

Hi All,
I want to know User Exit for MIGO Screen. when I click check button it will be show "Item OK " Field select or not.
MIGO Screen post if Item ok field select both parent id and line id . otherwise it will be show error message?.
Can Please every one tell me how to do user exit for MIGO?
mail id: [email protected]
thanks,
S.Muthu,

Hi,
check the BADI MB_MIGO_BADI ( method: POST_DOCUMENT).
COMD enhancment MBCF0005
Regards

How to create a webservice for sap transaction?

Hello All,
I developed a custom program and created a transaction for that? Is it possible to create a webservice for this custom transaction ? If yes,how should we ? I have seen many documents which all describing to creartion of webservice for an RFC only.
Please help in this regard...
Thanks ,
Ravi

Hello,
You cannot create a Web Service for an ABAP program/transaction directly. You have to move the logic into an RFC. Only RFC, BAPI & Business Object can be converted to Web Service using the Wizard.
Thanks,
Venu

How to create a RFC destination for extracting data to HANA

Hello All,
Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

Hi Venkatesh,
In SM59 t.code we create RFC destinations.
Go thru the video link for creating RFC destinations step by step
How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

How to create a macro for a planning type in MC8b transaction

Hi,
I am presently working for a product allocation demand, which have a information structiure with characteristic and key field.
the characteristic are production allocation quantity, incoming order quantity, and open order quantity.
i have created a planning type in which the data updation takes from the excel file to the planning type in mc95.
but i need to create a macro for this planning type .
can any body give the details information how to create a Macro for a planning type.
Thanks and regards
GopalKrishna

Dear Gopal
May be the link would be helpful to you.
[Planning Types and Macros|http://help.sap.com/saphelp_46c/helpdata/en/a5/631cc443a211d189410000e829fbbd/frameset.htm]
Drill down the left tab once you opened the link, for more information.
Thanks
G. Lakshmipathi

BADI FOR MIGO TRANSACTION

HI EXPERTS,
HOW CAN I ADD TWO SCREEN FIELDS FOR MIGO TRANSACTION?
HOW CAN THE TWO SCREEN CAN VALIDATE DATA FROM PURCHASE ORDER NO ENTERED?
CAN ANY ONE FIND A SOLUTION AND HELP ME THIS.

Hi,
You may create an implementation for the badi in SE19. Then the attributes will be available during runtime for the method, and you may use those to validate the data.
The BADI MB_DOCUMENT_BADI and method MB_DOCUMENT_BEFORE_UPDATE also triggred during MIGO and the structures XMKPF, XMSEG contains the runtime values for the document.
Regards,
Renjith Michael.
http://www.sourceveda.com/page4.htm

How to create custom infotype for training and event management

hai freinds can any one tell me how to create custom infotype for training and event managment with following fields
PS No PA0000-> PERNR
Name - PA0001 -> ENAME
IS PS.No. PA0001-> PS no. of Immediate Superior
IS name PA0001 -> ENAME
thanx in advance
afzal

Hi,
Your question is not clear for me. Since it is a TEM infotype, it could be a PD infotype.
If you wish to create a PD infotype, use transaction PPCI to create the infotype.
But before that you need to create a structure HRInnnn (where nnnn is the infotype number) with all the fields relevant for the infotype.
If you wish to create a PA infotype, use transaction PM01 to create the infotype.
But before that you may be required to create a strcuture PSnnnn (where nnnn is the infotype number) with all the fields relevant for the infotype.
Regards,
Srini

Bapi for migo transaction

i have created a bapi to upload data for MIGO transaction.. (GOODS RECEIPT-->PURCHASE ORDER)
i am getting the error " stock posting is not possible for this material "'.
when i create directly, it is posted.. while uploading through the program it shows the above error.
please suggest if anyone knows....
Thanks in advance,
Dhivya N.

*& Report ZR_MIGO_UPLOAD
*& package name : zabap
*& transport request number : MIDK901443
*& program to upload goods movement
REPORT ZR_MIGO_UPLOAD.
***DATA DECLARATION***
type-POOLs: icon.
TYPES: BEGIN OF TY_GR_PO,
 EBELN(10) TYPE c , "'PO NUMBEr
 EBELP(10) TYPE c, "PO ITEM NUMBER
* LGOBE TYPE LGOBE, "STORAGE LOCATION DESCRIPTION
 LGORT(10) TYPE c, "STORAGE LOCATION
 XFELD TYPE c, "ITEM OK
 GERNR(10) TYPE c, "SERIALNUMBER
 END OF TY_GR_PO.
DATA: TA_GR_PO TYPE TABLE OF TY_GR_PO, "TABLE FOR GOODS RECEIPT PURCHASE ORDER
 WA_GR_PO TYPE TY_GR_PO.
DATA: BLDAT TYPE BLDAT, "DOCUMENT DATE
 BUDAT TYPE BUDAT, "POSTING DATE
 WEVER TYPE WEVER. "VERSION FOR PRINTING GR SLIP
***BAPI DECLARATION***
DATA: BEGIN OF GM_HEAD OCCURS 0. "Material Document Header Data
 INCLUDE STRUCTURE BAPI2017_GM_HEAD_01.
DATA: END OF GM_HEAD.
DATA: BEGIN OF GM_CODE OCCURS 0.
 INCLUDE STRUCTURE BAPI2017_GM_CODE. "Assign Code to Transaction for Goods Movement
DATA: END OF GM_CODE.
DATA: BEGIN OF GM_RET OCCURS 0.
 INCLUDE STRUCTURE BAPI2017_GM_HEAD_RET. "Material Document Number/Material Document Year
DATA: END OF GM_RET.
DATA: BEGIN OF GM_ITEM OCCURS 0.
 INCLUDE STRUCTURE BAPI2017_GM_ITEM_CREATE. "Material Document Items
DATA: END OF GM_ITEM.
DATA: BEGIN OF GM_SER OCCURS 0.
 INCLUDE STRUCTURE BAPI2017_GM_SERIALNUMBER. "Serial Number
DATA: END OF GM_SER.
data: BEGIN OF ta_bapireturn OCCURS 0.
 INCLUDE STRUCTURE BAPIRET2.
data: END OF ta_bapireturn.
***declaration of excel file handling table***
FIELD-SYMBOLS: <fs> type any. "field symbol for alsm_excel
DATA: TA_EXCEL TYPE TABLE OF ALSMEX_TABLINE, "table to contain excel sheet values
 WA_EXCEL TYPE ALSMEX_TABLINE.
***declaration of other parameters***
data: V_brow type i VALUE 2, "BEGIN OF ROW
 V_bcol type i value 1, "BEGIN OF COL
 V_erow type i value 65536, "END OF ROW
 V_ecol type i value 256. "END OF COLUMN
DATA: V_sear type string,
 V_INDEX TYPE i,
 V_tabix type sy-tabix, "current line.
 v_lines type i. "total number of records
DATA: DATE TYPE DATS.
***SELECTION SCREEN***
***SELECTION SCREEN DESIGN***
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP 3.
PARAMETERS: zCODE(2) TYPE C MATCHCODE OBJECT H_T158G,
 zrefdoc type REFDOC,
 version type WEVER.
SELECTION-SCREEN skip 5.
PARAMETERS: p_file type ibipparms-path.
SELECTION-SCREEN SKIP 3.
SELECTION-SCREEN END OF BLOCK b1.
***SELECTION SCREEN VALUE REQUEST***
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
 CALL FUNCTION 'F4_FILENAME' "f4 help for file name
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = 'P_FILE'
 IMPORTING
 FILE_NAME = P_FILE.
***SELECTION SCREEN EVENT***
AT SELECTION-SCREEN. "validation
 if p_file <> ''.
 V_sear = p_file.
 SEARCH V_sear for '.xls'.
 if sy-subrc <> 0.
 message 'please provide excel file. it is not valid' type 'E'.
 ENDIF.
 ENDIF.
INITIALIZATION.
* DATE = '17.04.14'.
 GM_HEAD-PSTNG_DATE = SY-DATUM.
 GM_HEAD-DOC_DATE = SY-DATUM.
 gm_head-pr_uname = sy-uname.
***START OF SELECTION***
START-OF-SELECTION.
 gm_head-REF_DOC_NO = zrefdoc.
 gm_head-VER_GR_GI_SLIP = version.
 GM_CODE-GM_CODE = zCODE.
 PERFORM EXCEL_UPLOAD.
 PERFORM EXCEL_CONVERSION.
 PERFORM NO_RECORDS.
END-OF-SELECTION.
 PERFORM BAPI_ASSIGNMENT.
 PERFORM BAPI_FM.
*& Form EXCEL_UPLOAD
* text
* --> p1 text
* <-- p2 text
FORM EXCEL_UPLOAD .
 CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = V_BCOL
 I_BEGIN_ROW = V_BROW
 I_END_COL = V_ECOL
 I_END_ROW = V_EROW
 TABLES
 INTERN = TA_EXCEL
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
ENDFORM. " EXCEL_UPLOAD
*& Form EXCEL_CONVERSION
* text
* --> p1 text
* <-- p2 text
FORM EXCEL_CONVERSION .
 if ta_excel is NOT INITIAL.
 sort ta_excel by row col.
 clear wa_excel.
 clear wa_GR_PO.
 LOOP AT ta_excel INTO wa_excel.
 move wa_excel-col to v_index.
 ASSIGN COMPONENT v_index OF STRUCTURE wa_GR_PO to <fs>.
 if sy-subrc = 0.
 move wa_excel-value to <fs>.
 ENDIF.
 at END OF row.
 append wa_GR_PO to ta_GR_PO.
 clear wa_GR_PO.
 ENDAT.
 ENDLOOP.
 else.
 MESSAGE 'no data for conversion' type 'I'.
 ENDIF.
ENDFORM. " EXCEL_CONVERSION
*& Form NO_RECORDS
* text
* --> p1 text
* <-- p2 text
FORM NO_RECORDS .
 DESCRIBE TABLE ta_GR_PO LINES v_lines.
 if v_lines = 0.
 MESSAGE 'NO RECORDS TO UPLOAD' TYPE 'E'.
 ENDIF.
ENDFORM. " NO_RECORDS
*& Form BAPI_ASSIGNMENT
* text
* --> p1 text
* <-- p2 text
FORM BAPI_ASSIGNMENT .
 IF TA_GR_PO IS NOT INITIAL.
 LOOP AT TA_GR_PO INTO WA_GR_PO.
 gm_item-PO_NUMBER = wa_gr_po-ebeln.
 GM_ITEM-STGE_LOC = WA_GR_PO-LGORT.
 GM_ITEM-PO_ITEM = WA_GR_PO-EBELP.
 GM_ITEM-NO_MORE_GR = 'X'."WA_GR_PO-XFELD'.
* GM_SER-SERIALNO = WA_GR_PO-GERNR.
 gm_item-NO_MORE_GR = 1.
 gm_item-ENTRY_QNT = 2.
 gm_item-MOVE_TYPE = 101.
* gm_item-MVT_IND = 'B'.
 gm_item-plant = 'P001'.
 gm_item-move_stloc = 'FG01'.
* GM_ITEM-SPEC_STOCK = 'K'.
 APPEND GM_ITEM.
 APPEND GM_SER.
 ENDLOOP.
 ELSE.
 MESSAGE 'DATA IS NOT UPLOADED' TYPE 'I'.
 ENDIF.
ENDFORM. " BAPI_ASSIGNMENT
*& Form BAPI_FM
* text
* --> p1 text
* <-- p2 text
FORM BAPI_FM .
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 GOODSMVT_HEADER = gm_head
 GOODSMVT_CODE = gm_code
* TESTRUN = ' '
* GOODSMVT_REF_EWM =
IMPORTING
 GOODSMVT_HEADRET = gm_ret
* MATERIALDOCUMENT =
* MATDOCUMENTYEAR =
 TABLES
 GOODSMVT_ITEM = gm_item
 GOODSMVT_SERIALNUMBER = gm_ser
 RETURN = ta_bapireturn
* GOODSMVT_SERV_PART_DATA =
* EXTENSIONIN =
if ta_bapireturn-type = 'S'.
 write:/ icon_green_light as icon,
 'success: Material document',gm_ret-mat_doc, 'is created for the GOODS RECEIPT- po number : ', wa_gr_po-ebeln,
 / 'reason:' , ta_bapireturn-message.
ELSEIF ta_bapireturn-type = 'E'.
 write:/ icon_red_light as icon,
 'error: Material document',gm_ret-mat_doc , 'is not created for the GOOD RECEIPT- po number : ', wa_gr_po-ebeln,
 / 'reason:' , ta_bapireturn-message.
ENDIF.
ENDFORM. " BAPI_FM

How to create value request for screen field text box tt1

How to create value request for screen field text box tt1
i have a text box name tt1,
i want f4 help for that .
remember i am asking for screen i.e done from screen layout not selectio-screen.
Thank you,
Regards,
Jagrut Bharatkumar Shukla,

Hi,
Create one Search Help in the SE11 for the particular Field that u want to display. In the Screen(Transaction SE51),For that Text Box in the Attributes,in Dict Tab ->Search Help Field give that Search Help Name.
For Eg,
If u want Purchase Order Numbers in that F4 Help.Create one Search Help by giving Table Name as EKKO & Search Help Parameter as EBELN with Lpos & Rpos as 0 & 1.Save & Activate it.
Give this Search Help Name in Dict Tab ->Search Help Field of that Screen Attributes.
Regards,
Padmam.

How to create transport request for standard text created using SO10.

Hi,
How to create transport request for standard text created using SO10?
Regards
Ramakrishna L

Hi,
For the Standard text created in SO10,
please go to transaction SE78 -> FORM GRAPHICS->STORED AS TEXT->STANDARD TEXTS->
Double click on ADRS or ST or what ever your type of text->
Enter your standard text name
Click on transport button->SHIFT+f6-> It will ask you for a transport request.
Best regards,
Siva

How to create new version for material

Hi expert,
Can anyone please guide me step by step on how to create new version for material and vendor? Please also mention transaction and details step by step.
Thanks

HI,
Do you mean to have version management for purchasing documents?.
Best Regards,
Arminda Jack

How to create authorisation object for save button please help in abap

how to create authorisation object for save button please help in abap

Hi
In general different users will be given different authorizations based on their role in the orgn.
We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.
USe SUIM and SU21 T codes for this.
Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.
If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.
This means you have to allocate an authorization object in the definition of the transaction.
For example:
program an AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT <authorization object>
ID <authority field 1> FIELD <field value 1>.
ID <authority field 2> FIELD <field value 2>.
ID <authority-field n> FIELD <field value n>.
The OBJECT parameter specifies the authorization object.
The ID parameter specifies an authorization field (in the authorization object).
The FIELD parameter specifies a value for the authorization field.
The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.
http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.
You program the authorization check using the ABAP statement AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '02'
ID 'CUSTTYPE' FIELD 'B'.
IF SY-SUBRC <> 0.
MESSAGE E...
ENDIF.
'S_TRVL_BKS' is a auth. object
ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.
The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.
This Authorization concept is somewhat linked with BASIS people.
As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.
Take the help of the basis Guy and create and use.
Regards
ANJI

How to create a session using call transaction method.

hi , this is nagaraju,
How to create a session using call transaction method.

Hi,
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
     The first is when application data to be replaced is transferred at once, and only once.
     The second situation is to transfer data periodically from external systems to SAP and vice versa.
     There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. Unless session is processed, the data is not transferred to database table.
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program.
SESSION METHOD
Data is not updated in database table unless Session is processed.
No sy-subrc is returned.
Error log is created for error records.
Updation in database table is always synchronous
CALL TRANSACTION
Immediate updation in database table.
Sy-subrc is returned.
Errors need to be handled explicitly
Updation in database table can be synchronous Or Asynchronous.
Regards,
Sruthi.

How to create Charge indicator for Bank account

Dear SAP Gurus,
Please advice how to create charge indicator for bank account under - Set Up Bank Determination for Payment Transactions - activity in automatic outgoing payment configuration.
There is no customizing option in F1 help option. I also try to search in IMG there is also no link for the same.
Early reply would be appreciated.
Regards,
Prafful Kansal
9910432881

Dear,
Charge Indicator is freely definable field, you can put any value you want.....
Regards
Chintan Joshi

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

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

How to create an RFC for MIGO transaction?

Similar Messages

Maybe you are looking for