Assignment of function module in spro

Hi All,
We are using the Sabrix external system for tax calucation. They defined the function module for computation of tax. where do we assign the functional module in system.
Thanks and regards,
Ravi Vruddhula.

hi,
u want to specify ur customized FM here :
SPRO (Cross Application Components  SAP Business Partner  Business Partner  Tax Jurisdictions  Using SAP Software  Assign Function Module to Indicator)
thanks...

Similar Messages

Transaction code to assign the function module to the process code

Hi,
What is the transaction to assign the function module to the process code

Hello Preethi,
Try with these Tcodes:

WE41 0000 Process codes, outbound
WE42 RSECODIN 1000 Process codes, inbound
WE43 0000 Funct.module: Status record display
If useful reward.
Vasanth

How to defined/change assigned MW function module in CRMSUBTAB-MOD_NAME

Hi,
I need to find the place, where I can configure the field values of MOD_NAME in CRMSUBTAB. I am unable to find anything in R3AS3 for "CPB_STOCK_INFO". There is a function module "CRS_CP_STOCK_EXTRACT" assigned via CRMSUBTAB, which I have to replace by my own function module.
The values are actually stored in ERP, but as I saw in Program SAPLSMOFCUST (Include LSMOFCUSTFOU), it gets written down by CRM. I don't know how to locate the transaction code, which is using this program otherwise I would have solved my issue :o)
Thanks for any help!
Regards,
Andreas

I just found the solution! It was just not so obviously as the default function was not displayed. I have opend R3AS3 in CRM, selected "CPB_STOCK_INFO", went to the detail screen in edit mode and opened the popup behind the button of object class. The popup offers you a empty field and allows you to overwrite the SAP default module in the ERP table.
Regards,
Andreas

How to Assign a function module for customized IDOC

Hi,
I have created a customized IDOC. Can any body explain how to assign a FM for customized IDOC? Is same IDOC can be used for both Outbound and Inbound Process? In WE41 and WE42 we have to give the outbound and inbound function module name. can we give same function module? Is process code is same for both outbound and inbound process?
Valuable suggetions are appreciated.
Regards,
Ram

Hi ,
Here is the Procedure for the Inbound Idoc Funtion Module
Function Module : SE37
Message : WE81
Assign message : WE82
Assgin FM : we57
Process Code : WE42.
Assign Partner Profile - WE20,
To test the Inbound IDOC.
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...
Reward Points if it is Useful.
Thanks,
Manjunath MS

How could we assign customized function module to the object

Hi Experts,
How could we assign z made function module to the object type.
for instance, i have prepared one z function module and want to assign segment builder.
Please help in this regard
Thanks
Mahesh Babu

Hi Thiru,
Standard Transaction Codes, have their own Function Modules for generating Outbound/Indbound Idocs. Where these Function Modules will be configured to a particular Process Codes.
For E.g for PO's
Process code : ME10 - IDOC_OUTPUT_ORDERS - for creation
In case if its a Z Function Module, It depends on the case how you use IDOC types. either directly through Z Program or through Inbound/Outbound Process codes with respective Function modules.
Regards,
Anbalagan

How to assign Function Module in CT04

Hi all,
In CT04 we assign a function Module in the Values Tab. I read from SAP help on the interface to be used. But not clear on how to assign this correctly. If anybody who worked on this can give me an example. How we do declare the function when we write dependency?
Thanks,
Manjula.S

Hi
Created F4 function module with prefix _f4 but its not triggering my break point.
only assigned fm and _dc is triggering my fm...
what is the problem in my f4 fm?
FUNCTION zxxxx_f4.
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(CHARACT_NO) LIKE CABN-ATINN
*"     REFERENCE(CHARACT) LIKE CABN-ATNAM
*"     REFERENCE(DISPLAY) TYPE CHKBOX
*"     REFERENCE(ADDITIONAL_VALUES) LIKE CABN-ATSON
*"     REFERENCE(MULTIPLE_VALUES) TYPE RCTMV-ATLIS
*"     REFERENCE(LANGUAGE) TYPE SY-LANGU
*"     REFERENCE(DISPLAY_WITH_LANGUAGE) TYPE CHKBOX
*" TABLES
*"      VALUES STRUCTURE RCTVALUES

Help in Creation of a Function Module.

Hi Abapers,
                I am new to ABAP and hardly have knowledge abt it. I need to create a Function Module which is of the type RFC. Pls provide me information and steps to create the same.
Many thanks in Advance.

Hi Pooja,
Please follow the below steps to create a function module :
1. Goto Transaction code : SE37.
2. Create a Function Group first.
   a) From the Menu Bar Choose Goto -> Function groups -> Create group.
   b) Specify the function group name and a short text.
   c) Choose Save.
When you create a new function group, the system automatically creates a main program containing two includes. Like any other programs and includes, you can display them in the Repository Browser.
3. Now create a Function Module.
4. Enter the function's name in the field Function module.
5. Choose Create.
6. In the Enter function group dialog box, enter the function group to which you want to assign the function module.
7. In The Attributes Tab select Remote Enabled Module (since you want a RFC function module ).
8. Give the Import and Export parameters and exceptions(if any).
9. Write the functioning part of the fuction module in the Source code tab.
10. Save and Activate your function Module.
Now go ahead and use your function module where ever you want.
Hope it helps.
Reward if helpful.
Regards
Hemant Khemani

Function modules used in process message categories

Hi Gurus,
in process message characteristics, we need to assign the function modules. please advise is there any place (sap system or any website) where we can find all the function modules which are used in pi sheets? i want to know function modules and their uses or how to use them in pi sheets? if i want to develop new function modules, what should be the criteria, please guide me. thank you for the support.

Hello
In addition, on transaction O13C you will find the process message categories and which message destination is assigned to each category.
Here is the documentation of the message categories:
Predefined Process Message Categories - PP - PI-PCS Interface: Linking of Process Control Systems - SAP Library
BR
Caetano

Help in enhancing CRM logon function module

Hello all,
We have a situation where in the past we have allowed the creation of multiple Business Partners sharing the same e-mail address. We are about to close this loophole but we have this as a master data issue for some existing Customers/Business PArtners.
Currently, our CRM Webshop only uses e-mail address and password for login verification (not using Business Partner/Customer number).
We would like to enhance the webshop logon to include customer number as well ie. We want to determine which customer number associated with the ambiguous e-mail address is used. I have attempted to identify which function module is involved by inserting an endless WHILE loop into the following , but none of them seems to be called :
CRM_ICSS_USER_LOGIN
CRM_ISA_IUSER_LOGINr
CRM_ISAI_BP_LOGIN_BPARTNER_GET
CRM_ISA_BP_LOGIN_CHECK
CRM_ISA_LOGIN_R3USER_CHECK
CRM_ISA_IUSER_LOGIN
CRM_ISA_LOGIN_CHECK
CRM_ISAI_BP_LOGIN_BPARTNER_GET
In addition I notice the function SUSR_CHECK_LOGON_DATA can not be enhanced as it's a Basis FM.
I have attempted to look up documentation in SAP Help and not much joy. Can anyone tell me whether I'm barking up the wrong tree and this needs to be addressed by a kernel level function or recommend another place in the standard code ?
Regards,
Gabriel

Hi Pooja,
Please follow the below steps to create a function module :
1. Goto Transaction code : SE37.
2. Create a Function Group first.
   a) From the Menu Bar Choose Goto -> Function groups -> Create group.
   b) Specify the function group name and a short text.
   c) Choose Save.
When you create a new function group, the system automatically creates a main program containing two includes. Like any other programs and includes, you can display them in the Repository Browser.
3. Now create a Function Module.
4. Enter the function's name in the field Function module.
5. Choose Create.
6. In the Enter function group dialog box, enter the function group to which you want to assign the function module.
7. In The Attributes Tab select Remote Enabled Module (since you want a RFC function module ).
8. Give the Import and Export parameters and exceptions(if any).
9. Write the functioning part of the fuction module in the Source code tab.
10. Save and Activate your function Module.
Now go ahead and use your function module where ever you want.
Hope it helps.
Reward if helpful.
Regards
Hemant Khemani

XI-- IDOC scenario, how to link process code with function module

Hi Forum,
I have a XI--->IDOC (R/3) scenario,
where i m creating a IDOC in XI and sending it to R/3,
i have done all settings to send the IDOC from XI to the R/3,
i also have the function module to process that IDOC in R/3,
the problem is:
I want to know in details (step by step) how to make a Idoc Inbound process code, link it with the function module and use the process code in the Partner Profile in R/3,
pls help

HI,
FOr this u need to go to transaction WE41 for inbound and WE40 for outbound there u assign the function module.
Now u go to WE20 transaction for partner profile and u can assign the proces code to the inbound message.
Go to the below help for more information:
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Inbound process code:
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Thnx
Chirag

Transport of ALE Interfaces for Function Module

hi,
i have a Z function module, Z business object type and z message type identifying ALE interface.
i need to move all the objects from Dev R3 to QA R3. What are the steps involved?
Thanks,
Tirumal

Hi
While creating a Z function module it will ask you for a change request number. attach it to change request and migrate it to Production.
In case your function group to which you assigned this function module is open then the CTS number will by default come in CTS number field if any exists for the function group. You can now migrate your CTS to production.
Now after assinging function module to a CTS you can be sure that your program for function module and FM both will be migrated. For confirmation you can now check attribuutes section in your function module. it will list the SAP program associated with Func mod , function group to which function module is assigned , package and include programs which needs to be migrated. So you only need to attach a CTS and migrate your CTS.
You can create a Change erquest (CTS) in SE01 or SE10 transactions.
Regards,
Amit.
Please reward any help
Message was edited by: amit bhadauria
Message was edited by: amit bhadauria

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 error 51- Function module not allowed:

Hi,
I am getting following error in IDOC inbouond.I verifyed all parameters mentioned in error.
Issue still not resolved.
When debugged from WE19 this issue dosnt arise.
Kindly guide.
Function module not allowed: ZIDOC_INPUT_MATCLASS
Message no. B1252
Diagnosis
The function module ZIDOC_INPUT_MATCLASS and the application object type BUS1001 which were determined are not valid for this IDoc.
Procedure
1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.

Hi,
Check in WE42, for the process code, you have assigned this function module and given the correct process code in the partner profile.
Sujay

[IDOC] How to access IDOC in function module?

Hey,
I know how to assign an function module to an incoming IDOC.
Do I have to define the IDOC as import parameter or how to
access the data of the IDOC?
Anyone got a link to a short example?
regards
chris

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/03e6e790-0201-0010-9d98-ab8102817a92
refer section 5.2.2.4

IDOC ABAP-PI Port Function Module not called

HI all,
i am using a scenario where i am sending (outbound) idocs via abap proxy to PI.
I have assigned the function module to the abap-pi port.
when i am trying to send a test idoc via we19, i get the message "IDoc '0000000000198029' transferred to ABAP-PSS port".
but the function module (a copy of own_function) doesn't get called. if i am testing the function module from se80 with the above mentioned idoc number '0000000000198029' everything is fine.
in the partner profile i have added the corresponding idoc message type and selected to send idocs immediately. have i forgotten something in order to trigger the call of the function module ?
br,
martin

Hello,
I think it is not so easy to send IDoc to XI with ABAP-PSS-Port.
I would try to create the IDoc and send it to XI-Port (Transactional RFC).
This is SAP-Standard for IDoc-Scenario (SAP-R3 to XI).
Best Regards, Dirk

Assignment of function module in spro

Similar Messages

Maybe you are looking for