Assignment of BTE to Function Modules

Hi SAP guru's
Please tell me Where can i assign the following.
Assign the following BTE events to the corresponding function modules:
BTE     Function module
1025     CREATE_DEFTAX_ITEM
1030     SET_DEFTAX_ITEM
1040     CREATE_DEFTAX_ITEM_REVERS
1050     CREATE_DEFTAX_ITEM_MR1M
Before ECC 6.0 the path was as follows
You make this assignment in Customizing for Financial Accounting under Financial Accounting Global Settings -
> Business Transaction Events. From the menu on the screen SAP Business Framework: Business Transaction Events, choose Settings ---> P/S Modules ---> of an SAP Application.
Regards
Sujit

Hi Sujit,
Can you please provide answer for this.
Regards
Atul

Similar Messages

How can i get currency values from flatfile to function module

Dear All,
           I have to take currency values from flat file and i have to assign those flat file value to function module .
Eg: "Convert_to_local_currency". I need technical code how to calculate those amount in work area and how to assign those amount value function module.
          I need sample program for currency conversion from flat file to function module. My requirement is based on flat file amount i have to calculate in work area and assign those work area to function module.
With Regards,
Baskaran

Hi Satish or Baskaran,
First conform in which format the flat file is present, as abhi mentioned if it is there in notepad
try to use F.M GUI_UPLOAD as shown below...
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = 'C:\Desktop\rpf1.TXT'
TABLES
DATA_TAB = ITAB.
Now loop at ITAB Into Work_area and press the respect currency fields which you want and in the same way
if the file is in EXCEL format use F.M ALSM_EXCEL_TO_INTERNAL_TABLE
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      filename = P_FNAME
      i_begin_col = 1
      i_begin_row = 1
    TABLES
      intern = ITAB
LOOP AT ITAB INTO WA.
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
        EXPORTING
          foreign_currency = wa-waers
          local_currency   = wa-waers
           IMPORTING
          local_amount     = tvals-gross.
    ENDIF.
endloop.
And as mentioned loop the records into work area and process the currenct field which is present in the
ITAB according to its field name. And make sure within the loop you call your function module.
Regards
VEnk@
Edited by: Venkat Reddy on Dec 9, 2009 5:51 PM

Debugging Outbound Function module in EDI

Hello All,
I have a query regarding debugging function module which is used for creation of outbound Idoc for Purchase Order.
We have a Z process code which is assigned to a Z function module which creates an IDOC while a PO is created in the system.
But If I set break points in the Function module, the execution does stop there.
Can any one please tell me how to debug outbound processing Functioon module while PO is created.
Regards
Arindam

Hi,
There are 2 ways to to debug an outbound idoc triggered by an output type. One way is to set the output timing to 1, and save the purchase order and then execute RSNAST00 which will take the control to the breakpoint.
You can also debug the idoc with the output timing set as 4.
Here the idoc is triggered in update mode. Hence any breakpoints you may have set before will not reflect. Hence you need to activate update debugging.
Below are the steps for the same..
1. Add the output type in purchase order.
2. Enter '/h' to activate debugging in transaction window.
3. Save purchase order.
4. The process enters debugging mode.
5. In Settings tab, select checkbox for Update Debugging.
6. Click F8.
7. The control will appear to go out and re-enter debugging mode.
8. Now from the menu bar, in breakpoints option, choose Breakpoint At Function Module option, and give the name of the function module which is processing the idoc.
9. Once breakpoint set, click F8.
10. The control will now go to the function module. You can then debug the FM.
Hope this information is helpful.

Function Modul RV_SALES_DOCUMENT_VIEW_3

Hi all
i have a problem with the functionmodul RV_SALES_DOCUMENT_VIEW_3, when i run it, i became none data. I have enough authority, what's wrong?
Greezzzz
Moderator message: too vague, help not possible, please describe problems in all technical detail when posting again.
Edited by: Thomas Zloch on Nov 5, 2010 9:22 AM

Hi ,
I guess the function module 'RV_SALES_DOCUMENT_VIEW_3' should get called from the transaction to
display the list.
So for providing the access to this function module, you can create the single role (assigning the transaction of function module to this role) and then create the multple role and assign this multiple role to the user.
Please let me know for any issues.
Regards,
Darshana

How to add a created Z function module to the existing list in WE21

Hi all,
There is some existing function modules ( like EDI_PATH_CREATE_CLIENT_DOCNUM ) in WE21 in the function module field.
here, i need to create one Z function module as per user requirement & want to add to that list. is it possible???
actually, i want the file name format is like
" Document Number_YYYYMMDDHHMMSS.xml ". but existing function modules are not giving this format.do anybody give any idea.
correct answers will be rewarded.
Thanks & Regards

HI Pabitra,
Yes, can always change the existing fm and add it with message type as follows pls note step 7 and step 8. (for inbound it is we42 and for outbound it is we41 )
Basic IDOCs have supplied by SAP with standard structure. (Segments). You can extend them with your own segments.
IDOCs does have unique number. They contain control, data, and status records.
Useful Transaction Codes:
WEDI : IDoc Menu
WE02 : IDoc List (can enter IDoc number to select on)
WE05 : IDoc List
WE19 : Transaction WE19 can be used to test the IDoc
WE30 : IDoc Type Development: Initial Screen
WE31: Development Segments: Initial Screen
WE60 : Documentation for IDoc Types. This allows you to view the IDoc you have created.
WE81 : Display View EDI: Logical Message Types: Overview
WE82: Display View Message Types and Assignment to IDoc Types: Overview
WE21 - Creation of POrt
WE20 - Partner Profile creation
SALE - ALE (Application Linking and Enabling) settings
For Outbound ALE Configurations: (Example)
IDoc definitions and necessary ALE configurations settings for the outbound .
Create Idoc segments Transaction WE31.
Create Idoc type Transaction WE30.
Create Message Type Transaction WE81.
Assign Message Type to Idoc type Transaction WE82.
Create a distribution Model - Transaction BD64
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
for creating a IDOC
see the below steps for outbound processing IDOCS..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
The? name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
The segment should represent a structure in the program so for? each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
c_SEGMENT_type1.
The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
The ALE Layer handles the sending of the IDOC to the receiving system.
Error Handling (see Step 7b).
Commit work.
Project SpecificStep 7b Error Handling
Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
Declare a structure of type MCMAILOBJ for sending instructions.
Enter values for the internal table based on structure MCMAILOBJ
For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7
(Transaction WE57)
Assign the custom function module to the IDoc type and the message type.
Set function module to type F and direction 2 for inbound.
Step 8
(Transaction WE42)
Create a new process code and assign it to the function module. The process code determines how the incoming IDoc is to be processed in SAP.
Step 9
(Transaction BD67)
Assign the function module to the process code created above. Got to New Entries and enter the process code and the function module name.
Step 10
(Transaction WE20 and Transaction BD64)
Create a partner profile for your message and ensure that in transaction WE20 the process code is the one that points to your function module. (See step 6 of creating Outbound Idocs).
Step 11
Ensure that error handling functionality is present.
If u still have doubt, i can send u the print screen doc - hope this helps u
Reward pts if found usefull :)
regards
Sathish

IDOC: Incorrect function module problem

Hi,
I am working on inbound IDOC processing. I created an extension for an IDOC. I created custom segment & included it in the extension that I created. The Message type was also custom. (I merely copied an existing standard Message Type for some other purpose). I also assigned Function Module to Message Type & IDOC type. I have other necessary settings configured as required. The problem that I am encountering is as follows:
Incorrect function module IDOC_INPUT_SHPCPR called up
Message no. B1044
Diagnosis
The function module IDOC_INPUT_SHPCPR, which was called for the application input, was not able to process the IDoc. A possible cause is that the IDoc has wrong message type or IDoc type.
Procedure
Please check the message type assignment for the application function module in the ALE customizing.
Now to troubleshoot the above error, I made sure that I have an entry with FM. IDOC_INPUT_SHPCPR, IDOC Basic Type ,custom IDOC extension & custom Message Type. But even then I see the above error. This error appears as Status 51 for the test IDOC that I processed.
Can anyone please tell me how to solve this? Thanks in advance.

On line 49 of the function module :
* Loop through the IDocs' control records
LOOP AT idoc_contrl.
* Check the IDOCs message type
 current_mestyp = idoc_contrl-mestyp.
 PERFORM idoc_message_type_check
 TABLES idoc_status
 USING idoc_contrl
 mestyp-shpcpr
 CHANGING subrc.
Perform looks like this ( in Include LV56IF0C...)
FORM idoc_message_type_check
 TABLES t_idoc_status STRUCTURE bdidocstat
 USING f_idoc_contrl STRUCTURE edidc
 default_mestyp LIKE edidc-mestyp
 CHANGING subrc LIKE sy-subrc.
IF current_mestyp <> default_mestyp. " Here the variable default_mestyp has the value SHPCPR
 MESSAGE ID msg-id "Global variable
 TYPE 'E'
 NUMBER msg-nr_wrong_function "Global variable
 WITH current_mestyp "message type
 'IDOC_INPUT_SHIPPL'"Your function module
 f_idoc_contrl-sndprt "Sender partner type
 f_idoc_contrl-sndprn "Sender number
 RAISING wrong_function_called.
Again let me warn you that you will have to copy the entire function group V56I. Copying the function module alone will not help because there are many reusable subroutines in different includes of the function-pool.
regards,
Advait

Authorization for function module : RV_SALES_DOCUMENT_VIEW_3

hi,
the user does not have the auth for the fm RV_SALES_DOCUMENT_VIEW_3 and so he can not display the list that this fm is used in.
How can i provide this auth for this user?
Thanks.
Moderator message: not directly related to ABAP development, please have a look in Netweaver Security forum, but do not ask basic questions like this one.
Edited by: Thomas Zloch on Nov 8, 2010 12:41 PM

Hi ,
I guess the function module 'RV_SALES_DOCUMENT_VIEW_3' should get called from the transaction to
display the list.
So for providing the access to this function module, you can create the single role (assigning the transaction of function module to this role) and then create the multple role and assign this multiple role to the user.
Please let me know for any issues.
Regards,
Darshana

Initializing Function Module used in Planning function in BPS0

Hi Everybody,
 I have been assigned to create a function module which will be used for initialization purpose in BPS planning function. Whenever the user will change values of variable, even if user sets a data for a particular variable whose record does not exist in Cube, default values for keyfigyures should be shown after executing the planning function. How to achieve it? Eagerly waiting for your precious reply.
Warm Regards
Pulokesh

Hi Everbody,
 For a long time i have waited for somebody to answer my query. But after having all sorts of RNDs I came up with a sample code given below, and its also working properly....
FUNCTION ZKEYFIGURE_VALUE_DEFLT
""Local Interface:
*" IMPORTING
*" REFERENCE(I_AREA) TYPE UPC_Y_AREA
*" REFERENCE(I_PLEVEL) TYPE UPC_Y_PLEVEL
*" REFERENCE(I_METHOD) TYPE UPC_Y_METHOD
*" REFERENCE(I_PACKAGE) TYPE UPC_Y_PACKAGE
*" REFERENCE(I_LAYOUT) LIKE UPP_PARAM-PARAM DEFAULT 'INPUT'
*" REFERENCE(IT_EXITP) TYPE UPF_YT_EXITP
*" REFERENCE(ITO_CHASEL) TYPE UPC_YTO_CHASEL
*" REFERENCE(ITO_CHA) TYPE UPC_YTO_CHA
*" REFERENCE(ITO_KYF) TYPE UPC_YTO_KYF
*" EXPORTING
*" REFERENCE(ET_MESG) TYPE UPC_YT_MESG
*" REFERENCE(ETO_CHAS) TYPE ANY TABLE
DATA: LR_WA TYPE REF TO DATA.
DATA: T_SUBRC TYPE SY-SUBRC,
 LS_MESG TYPE UPC_YS_MESG,
 WA_COMDTY LIKE /BIC/PZCOMDTY.
DATA: L_COMDTY TYPE CHAR4, "Comodity value
 LS_CHASEL TYPE UPC_YS_CHASEL, "Line of characteristic selection table
 LT_CHARNG TYPE UPC_YT_CHARNG, "Selection table for char value
 LS_CHARNG TYPE UPC_YS_CHARNG, "line of selection table for char value
 L_VENDOR TYPE CHAR10, "VENDOR value
 LA_CHASEL TYPE UPC_YS_CHASEL, "Line of characteristic selection table
 LV_CHARNG TYPE UPC_YT_CHARNG, "Selection table for char value
 LA_CHARNG TYPE UPC_YS_CHARNG. "line of selection table for char value
FIELD-SYMBOLS: <LS_DATA> TYPE ANY,
 <CL_VEND> TYPE ANY,
 <CL_COMDTY> TYPE ANY,
 <KY_DATA> TYPE ANY,
 <S_CHAS> TYPE ANY,
 <FS_VEND> TYPE ANY,
 <FS_COMM> TYPE ANY.
IF T_SUBRC = 0.
*Get the comodity of the data begin processed
 READ TABLE ITO_CHASEL WITH KEY CHANM = 'ZCOMDTY3' INTO LS_CHASEL.
*Get the selection criteria comodity to be processed
 READ TABLE LS_CHASEL-T_CHARNG INDEX 1 INTO LS_CHARNG.
*Read the comodity from the selection criteria
 L_COMDTY = LS_CHARNG-LOW.
*Get the VENDOR of the data begin processed
 READ TABLE ITO_CHASEL WITH KEY CHANM = 'ZSS_VEND3' INTO LA_CHASEL.
*Get the selection criteria VENDOR to be processed
 READ TABLE LA_CHASEL-T_CHARNG INDEX 1 INTO LA_CHARNG.
*Read the VENDOR from the selection criteria
 L_VENDOR = LA_CHARNG-LOW.
create structure for the selection criteria
 CREATE DATA LR_WA LIKE LINE OF ETO_CHAS.
 ASSIGN LR_WA->* TO <S_CHAS>.
 ASSIGN COMPONENT 'ZSS_VEND3' OF STRUCTURE <S_CHAS> TO <FS_VEND>.
 IF SY-SUBRC EQ 0.
 MOVE L_VENDOR TO <FS_VEND>.
 ENDIF.
 ASSIGN COMPONENT 'ZCOMDTY3' OF STRUCTURE <S_CHAS> TO <FS_COMM>.
 IF SY-SUBRC EQ 0.
 MOVE L_COMDTY TO <FS_COMM>.
 ENDIF.
 COLLECT <S_CHAS> INTO ETO_CHAS.
ELSE.
 LS_MESG-MSGTY = 'W'.
 LS_MESG-MSGID = 'upf'.
 LS_MESG-MSGNO = '001'.
 LS_MESG-MSGV1 = 'Failed to get data from Layout'.
 APPEND LS_MESG TO ET_MESG.
ENDIF.
ENDFUNCTION.

BTE Name in Called Function Module

Hello,
A function module say XYZ is called from a BTE. Can I know the name of the BTE which called the function module XYZ inside the function module XYZ ?
With Regards,
Avisesh.

I think this document may help you...
Business Transaction Events
This activity describes how you can connect additional components (such as in the form of function modules developed yourself or a product from an external software provider) to the standard R/3 System.
There are two types of interface available in the General Ledger
Accounting (FI-GL), Accounts Receivable and Accounts Payable
(FI-AR/FI-AP), and Sales and Distribution (SD) components for this:
1. Publish & Subscribe interfaces (also called "informing interfaces" in the following) These should inform you about particular events (such as a document being entered) in the SAP standard application and make the data generated as a result available to the external software. The external software does not return any data to the standard R/3 System.
(I'm confused. MIT is using two business transaction events for the SD to FI interface. Both of these events are Publish & Subscribe interfaces. They both return data to the SAP standard application! They both change the FI document before it is posted. What I've figured out is that if there is an export to memory and an import from memory before and after the function call, then we can't modify the data. We can check this in the calling function module - OUTBOUND_CALL_00503110_E or OPEN_FI_PERFORM_00001020_E, etc)
Examples of such events in the R/3 System are:
Master record was created, changed, or blocked
Document was entered, parked, changed, or reversed
Items were cleared or reset
Additional processing can be caused in the additional component on the basis of these events and data:
Starting a workflow
Generating or changing additional data
Requesting correspondence
FI Clearing (F-32) calls (gathered via SE30):
Function OPEN_FI_PERFORM_00001020_E (can't modify data)
00001020 POST DOCUMENT: Prior to final checks
EVENT
This Event is reached prior to completing the document. The checks that are carried out at this point include checking, prior to posting, that the document balances to zero, and calculations for tax offsetting. This Event is accessed once per standard posting process and is similar to validation at document level (Event 0003). A document number has not yet
been assigned when this Event is reached.
INTERFACE
All document line items created and the document header data are
transferred (both as tables).
Parameter
T_BSEG
T_BKPF
Function OPEN_FI_PERFORM_00001025_E (can't modify data)
00001025 POST DOCUMENT: Final checks completed
EVENT
This Event lies following all checks on the whole document, but prior to number assignment. Following this Event, no further error messages may be sent. The document is complete at this point, and no further changes can be made to it prior to posting.
INTERFACE
All current data, all document data relevant for the posting, and various control parameters are transferred to the additional component. At this point you can still implement your own checks on the current document data.
Parameter
I_BKDF
T_AUSZ1
T_AUSZ2
T_AUSZ3
T_BKP1
T_BKPF
T_BSEC
T_BSED
T_BSEG
T_BSET
T_BSEU
Function OPEN_FI_PERFORM_00001030_E (can't modify data)
Function OPEN_FI_PERFORM_00001140_E (can't modify data)
2. Process interfaces (also referred to as "process" in the following) Process interfaces are used to submit business processes to a different control which cannot be realized with the standard system, that is process interfaces replace standard processes. Here you can structure determination of individual field contents or of specific reactions to process flows individually. It is possible to connect different external developments to the standard R/3 System. The additional developments are generally carried out using the ABAP/4 Development Workbench. This way you can, for example, influence the control of payment transactions. Selection of payment method, house bank and partner bank can be made using the payment data (currency, amount, and payee) according to a selection logic which you have defined.
FI Clearing (F-32) calls:
Function OPEN_FI_PERFORM_00001120_P
Function OPEN_FI_PERFORM_00001130_P
Function OPEN_FI_PERFORM_00001150_P
Function OPEN_FI_PERFORM_00001170_P
Standard Settings
Sample modules are delivered in the standard R/3 System which you can
copy into your name range and fill them with statements there.
Activities
1. Enter a product using "Settings -> Customer's products". Actually, in 4.6C, from transaction FIBF (IMG -> Financial Accounting -> Financial Accounting Global
Settings -> Business Transaction Events):
Settings -> Products -> ...of a customer
There are generally a large number of function modules belonging to a product which can be called by different program events from within the standard R/3 System. A product can also be an external software component. If the product is in an external system, enter an RFC destination here. If the product is in the same system, you do not have to enter anything. Important: Do not forget to activate the product after making the following settings.
2. Establish the interfaces with which the R/3 System provides you. To do this, choose
Environment -> Info system (P/S)
or
Environment -> Info system (Processes).
Execute the program. You should enter "A" as the
attribute type. You see the respective interfaces with which the R/3 System provides you. Note the key of the interface which you require.
You can also select:
By particular SAP application components
By particular events by entering intervals
Which interfaces are used in activated products
Which interfaces are used within a particular country version or within a particular industry
Which interfaces are used within a particular customer product
3. Enter the function module which you have developed yourself. To do this, choose either Goto -> Edit modules within the info system or Settings -> P/S modules or Process modules -> Customer's in the "SAP Business Framework" menu. Make the following entries:
Key for the interface
The product that you want to use
Function module which belongs to this product.
You can also enter several function modules for a product. Caution:
The function module must be within your name range, that is must begin with the letter Z. You leave the Ctr and Appl. fields blank unless you want a particular country version or a particular SAP industry-specific component to be enhanced or replaced instead of the standard process flow.
4. Fill the source text of your function module
and activate it. To do this, go again via Environment -> Info system (P/S) or Environment -> Info system (Processes) into the information system and execute the program. Then proceed as follows:
Click twice on the interface you have chosen. If you want, you can look at the interface at this point by choosing Goto -> Interface. Then choose the Back function again afterwards.
Place the cursor on the relevant line and choose Goto -> Function library. You see the sample function module delivered by SAP.
Copy the sample module delivered by SAP and call it the same as the function module entered in step 3.
Fill the source text of the empty function module.
Activate the function module.
Activate the product as described in step 1.
5. Run the R/3 program affected and test whether calling your function module works.
Further Notes
The other menu paths are only used for information about additional components delivered by SAP or about software already installed by external software providers.

Function Module to Validate a Partner Assignement to a Customer(XD02)

Hi,
I need a function module to check the validation,
while we assigning a partner to a customer in the customer master.
I need to replicate the SAP functionality in this case.
Thanks,
Sekhar.J

Hi,
Try
BAPI_CUSTOMER_CHECKEXISTENCE
BAPI_BUSPARTNER_CHANGE
BAPI_BUSPARTNER_CREATE
BAPI_BUSPARTNER_GETDETAIL
Edited by: Neenu Jose on Nov 3, 2008 6:04 AM

Function module for assigning BP Number to the Postion ID in org model

Hi Experts,
Is there any function module for assigning BP Number to the Postion ID in organizational model.
The requirement is:
1)There are some employees which are reporting to a Manager who has a position ID.
2) Each of these employees should be assigned to the given position ID.
This can be done by First Locate the BP Record in SAP via the Vantive Person ID and retrieve the SAP BP Number.
Then assign the SAP BP Number found to the Position ID.
My question is Is there any function module for assigning BP Number to the Postion ID .
Looking forward for reply.
Thanks & Regards,
Renju.

Hi,
Org. management uses API classe objects with static methods as APIs. You may be able to achieve this using
CL_CRM_ORGMAN_SERVICES->MAPPING_ORGUNIT_TO_BP
Reward if helpful!
Regards,
Sudipta.

Function module for assigning a HU to delivery

Function module for assigning a HU in HU managed location to a delivery ??

Hello,
In FuGrp HU_BASIC_BAPIS Basic BAPIs for Hus
with F’tn BAPI_HU_CREATE Create handling unit with items
this creates HU's NOT yet assigned.
After F'tn BAPI_TRANSACTION_COMMIT
You can assign the HU via
F'tn BAPI_HU_CHANGE_HEADER
using the BAPIHUHEADER fields: PACK_MAT_OBJECT & PACK_MAT_OBJ_KEY.
Dirk

Function module to get the wbs element by entering Assignment No.

Is there any Function module to get the wbs element by entering Assignment No.???????
Thanks and regards
Manish Thakur

hi Manish,
Just look at this function module.
function wbs_assignment_check.
""Lokale Schnittstelle:
*" IMPORTING
*"     REFERENCE(I_COMPONENT) LIKE RESBDGET STRUCTURE RESBDGET
*"     REFERENCE(I_PSPEL) LIKE RESB-PSPEL
*"     REFERENCE(I_RFPNT) LIKE AFVC-RFPNT
*" EXPORTING
*"     REFERENCE(E_PSPEL) LIKE RESB-PSPEL
e_pspel = i_pspel.
endfunction.
hope this helps u
REWARD IF USEFUL
thanks and regards
suma sailaja

Function module to update operation assignment for a BOM Item

Hi Group,
we have a requirement as under:
Goto BOM Change using CS02->select any BOM item and click the Menu path->Extras->Operation Assignment; and check one or more Operations and then save the transaction.
The above functionality has to be achieved through an Upload program(using Excel) with a Function module/BAPI to serve our purpose. we already did the functionality upto creation of BOM but could not proceed further on this current requirement.
Kindly let me know your inputs if you have already worked in such type of requirement.
thanks in advance for your inputs and let me know if any further info is needed.
Regards,
Vishnu

Hi,
Check the Bapis for BOM
BAPI_MATERIAL_BOM_GROUP_CREATE
CSAP_MAT_BOM_MAINTAIN
I hope second BAPI will be more usefull for your requirement.
Regards,
Goutam Kolluru.

Function Module to Insert Agent assignment upon creation of Responsibility

Hi Friends,
Using BDC I am able to create Resposibilities in Responsibilities tab of PFAC tcode.
I need to insert Agent assignment under created Responsibility.
Actually In Tcode PFAC I enter Rule then select change button this will lead us to next screen there i select Responsibilities tab
there I select create button then it will give a pop-up in that i will enter Object abbr. and Name then i will select continue.
then next i will enter category then select save.
Up to this using recording I am able to create Responsibilities but here i need to come back and i need to select just now created
Responsibility and i need to select insert agent assignment icon then it will give popup there i need to select Orgnizational unit then continue then it will give small popup ther i need to give search term (what ever we entered in Object abbr.) then continue again one popup will come ther we need to select that Org.unit check box then continue then it will one more popup there i need to select create then it will be inserted under Responsibilitty.
In the above entire explanation I am able do upto create Responsibilities but to insert agent assignment we need to come back after save but it is not possible through Recording because after save Recording will be ended.
So could you please guid me how to insert agent assignment under just created Responsibility.
If there is any function module to do that please suggest me .
Thanks
Chandu

Hi,
I tried like that also.
Whenever we need to insert agent assignment under just created Responsibility we need to select just created responsibility
created by first BDC . But in seccond BDC WITH TCODE OOCU_RESP Recording is not capturing that action (selecting just created Responsibility).
It is giving the message 'You did not select a valid object' in the status bar.
So It is unable to insert agent assignment under responsibility.
I think there would a function module which insert agent assignment under selected responsibility.
If anybody knows please suggest me or am I making any mistake ?
If you would like to see my code pls find below.
*& Report YCRM_CREATE_REPBLT_AGENT
REPORT ycrm_create_repblt_agent.
*Selection Screen
PARAMETERS : p_rule TYPE pdtask-seark OBLIGATORY,
 p_file TYPE rlgrap-filename OBLIGATORY.
*Data Declarations
TYPES : BEGIN OF ty_resp,
 short TYPE p1000-short,
 stext TYPE p1000-stext,
 category TYPE ro_expr, "EDIT_BIND_DEF-EXPR_LOW(02),
 END OF ty_resp.
DATA : it_resp TYPE TABLE OF ty_resp,
 wa_resp TYPE ty_resp,
 p_file1 TYPE string.
DATA : it_bdcdata TYPE TABLE OF bdcdata,
 wa_bdcdata TYPE bdcdata,
 it_bdcmsgcoll TYPE TABLE OF bdcmsgcoll,
 wa_bdcmsgcoll TYPE bdcmsgcoll.
*Constants Declarations
CONSTANTS : c_x TYPE c VALUE 'X',
 c_tcode(4) TYPE c VALUE 'PFAC',
 c_mode TYPE c VALUE 'A'.
*AT SELECTION-SCREEN event for providing f4 help for input file
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
PERFORM file_on_f4.
*Start of selectin event.
START-OF-SELECTION.
File Upload
PERFORM upload_file.
*BDC Logic
PERFORM bdc_to_create_rep.
*& Form BDC_DYNPRO
 text
 -->P_0061 text
 -->P_0062 text
FORM bdc_dynpro USING fp_program "value(p_0061)
 fp_dynpro. "value(p_0062).
CLEAR wa_bdcdata.
wa_bdcdata-program = fp_program.
wa_bdcdata-dynpro = fp_dynpro.
wa_bdcdata-dynbegin = c_x.
APPEND wa_bdcdata TO it_bdcdata.
ENDFORM. " BDC_DYNPRO
*& Form BDC_FIELD
 text
 -->P_0066 text
 -->P_0067 text
FORM bdc_field USING fp_fnam "value(p_0066)
 fp_fval. "value(p_0067).
CLEAR wa_bdcdata.
wa_bdcdata-fnam = fp_fnam.
wa_bdcdata-fval = fp_fval.
*WA_BDCDATA-DYNBEGIN = C_X.
APPEND wa_bdcdata TO it_bdcdata.
ENDFORM. " BDC_FIELD
*& Form FILE_ON_F4
 text
--> p1 text
<-- p2 text
FORM file_on_f4 .
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 field_name = 'P_FILE'
 CHANGING
 file_name = p_file
 EXCEPTIONS
 mask_too_long = 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.
ENDFORM. " FILE_ON_F4
*& Form UPLOAD_FILE
 text
--> p1 text
<-- p2 text
FORM upload_file .
p_file1 = p_file.
CALL METHOD cl_gui_frontend_services=>gui_upload
 EXPORTING
 filename = p_file1
 has_field_separator = 'X'
 CHANGING
 data_tab = it_resp
 EXCEPTIONS
 file_open_error = 1
 file_read_error = 2
 no_batch = 3
 gui_refuse_filetransfer = 4
 invalid_type = 5
 no_authority = 6
 unknown_error = 7
 bad_data_format = 8
 header_not_allowed = 9
 separator_not_allowed = 10
 header_too_long = 11
 unknown_dp_error = 12
 access_denied = 13
 dp_out_of_memory = 14
 disk_full = 15
 dp_timeout = 16
 not_supported_by_gui = 17
 error_no_gui = 18
 OTHERS = 19.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " UPLOAD_FILE
*& Form BDC_TO_CREATE_REP
 text
--> p1 text
<-- p2 text
FORM bdc_to_create_rep .
LOOP AT it_resp INTO wa_resp.
 REFRESH : it_bdcdata,
 it_bdcmsgcoll.
*Screen 0600
 PERFORM bdc_dynpro USING 'SAPLRHWS' '0600'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'PDTASK-SEARK'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=AEND'.
 PERFORM bdc_field USING 'PDTASK-SEARK'
 p_rule. "'90000159'.
*Screen 0040
 PERFORM bdc_dynpro USING 'SAPLRHWS' '0040'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=RESP'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'HRS1000-SHORT'.
 PERFORM bdc_field USING 'HRS1000-SHORT'
 'Z99999999972'.
 PERFORM bdc_field USING 'HRS1000-STEXT'
 'Category (RUN -SUPPORT) + C&PS Web'.
 PERFORM bdc_field USING 'HRS1203-ACTOR_FLAG'
 'R'.
*Screen 0040
 PERFORM bdc_dynpro USING 'SAPLRHWS' '0040'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=INSE'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'DATESET'.
 PERFORM bdc_field USING 'DATESET'
 'O'.
*Screen 0300
 PERFORM bdc_dynpro USING 'SAPLSPO4' '0300'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'SVALD-VALUE(02)'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=FURT'.
 PERFORM bdc_field USING 'SVALD-VALUE(01)'
 wa_resp-short. "'PL-BK'.
 PERFORM bdc_field USING 'SVALD-VALUE(02)'
 wa_resp-stext. "'Plan - BendixKing Team'.
*Screen 0200
 PERFORM bdc_dynpro USING 'SAPLRHUZ' '0200'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'EDIT_BIND_DEF-EXPR_LOW(02)'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=SAVE'.
 PERFORM bdc_field USING 'P1000-BEGDA'
 '23.03.2011'.
 perform bdc_field using 'P1000-ENDDA'
 '31.12.9999'.
 PERFORM bdc_field USING 'P1000-SHORT'
 wa_resp-short. "'PL-BK'.
 PERFORM bdc_field USING 'P1000-STEXT'
 wa_resp-stext. "'Plan - BendixKing Team'.
 PERFORM bdc_field USING 'EDIT_BIND_DEF-EXPR_LOW(02)'
 wa_resp-category. "'z11'.
 CALL TRANSACTION c_tcode USING it_bdcdata
 MODE c_mode
 MESSAGES INTO it_bdcmsgcoll.
 IF sy-subrc <> 0.
 MESSAGE i001(ymsg)."Error Message
 ROLLBACK WORK.
 ELSE.
 REFRESH : it_bdcdata,
 it_bdcmsgcoll.
**screen 0410
 PERFORM bdc_dynpro USING 'SAPLRHUZ' '0410'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'P1000-OBJID'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=CHG'.
 PERFORM bdc_field USING 'P1000-OBJID'
 p_rule. "'90000162'.
**screen 0420
 PERFORM bdc_dynpro USING 'SAPLRHUZ' '0420'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=RELI'.
 PERFORM bdc_field USING 'DATESET'
 'O'.
**screen 0110
 PERFORM bdc_dynpro USING 'SAPLRHW0' '0110'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=CONT'.
**screen 0100
 PERFORM bdc_dynpro USING 'SAPLRHWL' '0100'.
*perform bdc_field using 'BDC_CURSOR'
 'PCHDY-SEARK'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=CONT'.
 PERFORM bdc_field USING 'PCHDY-SEARK'
 wa_resp-short. "'PL-BK'.
**screen 0120
 PERFORM bdc_dynpro USING 'SAPMSSY0' '0120'.
*perform bdc_field using 'BDC_CURSOR'
 '04/03'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=ENTR'.
**screen 0400
 PERFORM bdc_dynpro USING 'SAPLRHUA' '0400'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=INSE'.
*perform bdc_field using 'BDC_CURSOR'
 'PERIOD-BEGDA'.
 PERFORM bdc_field USING 'PERIOD-BEGDA'
 '29.03.2011'.
 PERFORM bdc_field USING 'PERIOD-ENDDA'
 '31.12.9999'.
 CALL TRANSACTION 'OOCU_RESP' USING it_bdcdata
 MODE c_mode
 MESSAGES INTO it_bdcmsgcoll.
 IF sy-subrc <> 0.
 MESSAGE i001(ymsg)."Error Message
 ROLLBACK WORK.
 ELSE.
 MESSAGE i000(ymsg)."Success Message
 ENDIF.
 ENDIF.
ENDLOOP.
ENDFORM. " BDC_TO_CREATE_REP
Guide me on this.
Thanks

Assignment of BTE to Function Modules

Similar Messages

Maybe you are looking for