User Exit to call program to create IDocs.

Hi All,
For any creation/changes of material master using MM01/MM02 (after save ) one of the user exit will trigger.
From the user exit, I have to call the custom program to create MATMAS IDOCs.
if any failures in changes/creation of material master. It has to roll back eveything created by program.
Please let me know how to achieve this with out calling an event.
Thanks - Vinay

There are a number of standard methods to automatically create the IDOC. You can activate the change pointers and depending on need, use BD64 to create a distribution model, and create the necessary WE20 setups to create the outbound IDOC.
If you have to process the IDOC using custom logic, you can define that as well - although it's not clear why you need a custom generating program. You can insert code into one of the IDOC user-exits to manipulate the content if needed. Also, don't overlook the pre-delivered stuff from SAP that provides filtering out of segments and the like.
There are a few good SAP PRess books about doing ALE distribution -- if this is an unfamiliar area, it's worth the cost to buy one -- if you spend any time around IDOCS, you'll appreciate it.

Similar Messages

User-exit for call new customize screen of another new program

Hello, I'm very appreciate for all who read this topic and give me some advice.
Anyone has an experience about customize standard program to create new screen
and add new screen to pop-up when user click some standard button to do something
for support business requirement and then continue to working the old step (such next old screen).
In QA11 (Manual UD), For posting stock quantity (After click button "Stock for inspection lot")
Business requirement need to avoid user to input stock quantity for unrestriced used (UR) and block
by after click button "Stock for inspection lot". Need to customize to pop-up new created screen for user
to choose sub-set of this inspection lot to post for UR or block by check box (Just overview)
Then after finish to select, Need to go back old screen ("Record UD : Stock" Screen) and default sum
of UR and block into screen (Automatic) for post to mvt.type 321, 350 later.
After checked, Not have any screen-exit after clicked button "Stock for inspection lot".
but i found 1 user-exit which was called after click above button.
So, Can i use user-exit to call new customize screen?
If need to go back from new customize screen to main screen, May have any problem? How to do it?
If finish to do in new customzie screen and need to continue display next old screen. How to do it in PAI of new customize screen.
Thank in advance

Can anyone provide the documentation for this BADI? Also, I'm concerned about the layout of the screen. Can this BADI do the necessary changes on the layout of the screen?
Thanks!

User Exit in the Sales order create BAPI

Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.

Hi
User Exits In Sales Document Processing
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.

User Exit / BADi for TCode - IMA11 (Create Appropriation Request )

Hi friends ,
            Can anyone help me in finding the User Exit / BADI for Transaction IMA11 (Create Appropriation Request , Module - FI ).I want to create search help for field "Partner" in table control "Person Involved" present in this transaction.
Thanks in advance.
Regards
Nand Kishor

Hi,
The following user exits are available :
Exit Name           Description
AAIR0001            IM-IS: User value fields in app.req. reporting
AAIR0002            IM-FA: User fields for app. requests
AAIR0003            IM: Workplace assignmt when creating PM order from app.req.
AAIR0004            IM Drilldown: Definition of User-Defined Characteristics
AAIR0006            IM-FA-IA: Data Transfer from App. Req. to WBS Element
regards
Aveek

We create proforma invoice for a sales order.If the object status for the sales order is changed we have to add an output type that is record should be added to NAST table.User exit/Function Module/program .

Please provide me with a solution

Q1. will it charge material price to work order automatically ?
No you have to go with user exit for this
Q2. Unless the business is so specific such that they would like to treat this activity via sales, there is no significance in capturing the activity via SD. Perhaps, I would say, MM route is more appropriate.
Q3. The above holds good. That you go with MM route.
G. Lakshmipathi

User exit not getting triggered while creating the vendor

Hi all,
I wanted to extend the idoc(crermas01) according to my reqiurement.
But when I am trying to create a vendor using the IDOC cremas01 the user exit EXIT_SAPLKD01_001 is not getting triggered.
Can anybody tell me the reason why it is happening so...........
Thanks and regards,
Vinil.

Is your Idoc generated after the execution?
Where is you break-point, it is inside EXIT_SAPLKD01_001. Please note FM EXIT_SAPLKD01_001 will not be called unless it is implemented using project (CMOD) and project is active.

User exit to update extended segment in idoc for va01

Hi Experts,
I am working on Outbound IDOC interface for VA02 and VA01
I am using ORDERS05 IDOC type
i want to create one custom segment
and i want to fill that custom segment
but i am not able to find user exit to update this custom segment
please help.

Akshay,
I think you want to send order response for the orders created via Va01 or edited by Va02
To do this steps are:-
1) Use FM IDOC_OUTPUT_ORDRSP to send order response (ORDERS05)
2) Find the function exits in this Fm using search string as " Call Customer-function".
3) Use include in the exits to write code to append new segments to the IDOC. Look for the Tables parameter in the Exits which are of structure type EDIDD. Insert new Segment details in this table and your IDOC will be generated with required values.
Hope this helps!!
Harry

User Exit RV60AFZZ not Triggered When Processing IDOC

Hi,
I'm writing to seek some advice on why is the user exit RV60AFZZ not getting triggered when I do a vf01 bdc inside my inbouund IDOC function module. But when I try SHDB the user exit is getting triggered normally.
Thanks,
Mawi

Hi,
Yes I'm creating invoice using delivery orders, inside the idoc function module I'm using bdc call transaction vf01 but somehow it does not trigger the user exit.
But when I do manual vf01 in sap, the user exit is getting triggered.
I cant figure out why this is the behavior of sap.
Regards,
Mawi

User exit in Z program

Hello all,
I have copied a standard program to a Z program.
The standard program as a user-exit, but in the Z program this user-exit won't work. Does anyone know what i have to do so it will work?
Thanks in advance,
Nuno Silva

Hi
User exit is similar piece of code wirtten in the funtion module.
so if you copied a standrad program into a Z program the user exit will get triggerd if it not got triggred. Copy that function module into a Z funtion module and try to call that Z functionmodule in your Z program.
Regards,
Kiran.

Needs R/3 User-exit help when PO/PR created in Backend system

Hi SRM/MM Experts,
We are using ERP2005 and SRM 5.0 with classic scenario. Shopping cart converts the Purchase Requisition and Purchase Order in the backend system.
R/3 system had a custom logic to blank out the Account assignment category, cost center information when particular material group(ZZZZ0001), plant(Z0001) and storage location(Z01) used in the PO/PR that are created by SRM SC. The custom logic is used in user-exit- EXIT_SAPLMEWP_002- INCLUDE ZXMEWU06 and
EXIT_SAPLMEWQ_001-INCLUDE ZXMEWU04 of R/3 system. But now this custom functionality is not working. And I found out that when PO/PR is created by SRMs SC, include- ZXMEWU06 & ZXMEWU04 are not being called.
In which user-exit we should put custom logic in the R/3 system, so that it will be called for blanking out the Account assignment information, when SC is converted into PO/PR in the backend system
Thank you!
MP

Disha,
I figured out that we have to use user-exit:EXIT_SAPL2012_003 in R/3 system. Now here is what I am doing... If it is at non-stock material and it uses account assignment category-K and Cost Center-Z1000001, then I am blanking out the POITEM-ACCTASSCAT and POACCOUNT-DELETE_IND = 'X', but still it is not blanking out or deleting the account assignment information from PO.
Please let me know if this is the correct BADI to use to blank out the account assignment information in PO created by SC(SRM 5.0) in ECC 6.0. If yes, what should I need to do to blank out the account assignment information.
Any help is appreciated!
Thanks!
MP

User exit or Badi for VL31N (create inbound delivery)

Dear friends.
          I wish to add a check before saving in the transaction VL31N for that i need to know user exit or BADI..can you help me to know what possible user exit or badi available for this task.. your suggestion and article will be greate help of mine,
thanking you
regards,
Naim

Exit Name           Description
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of stock for POs for shipping due date list
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
BADI
<b>DELIVERY_PUBLISH</b>regards
vinod

The user exit EXIT_RFEBBU10_001 calls (the transaction FEBAN)

Hi,
we are using FEBAN transaction. Some customization was required to modify FEBEP/FEBRE fields.
While implementing this in EXIT_RFEBBU10_001 it was noticed that this exit is called for all unprocessed lines from the bank statement, NOT only for the item we have chosen to post.
e.g.
the bank statement has unprocessed 20 lines and we would like to post only one of them. this exit is called 20 times in spite of the fact that we have choose posting only 1 line in the FEBAN.
I was not able to identify in this user exit the items we are actually posting with FEBAN and ignoring all other unprocessed items from the same bank statement.
the R_KUKEY is being passed to rfebbu00 and to the exit but I couldn't find where to get ESNUM of the item being posted?
Is it actually possible to do?
thanks
victor

Thanks, Martin!
but I am afraid I was not clear in my question.the EXIT_RFEBBU10_001 works less or more fine for us when called from the FEBAN. (the 2nd step, i.e. postprocessing after uploading) .
while doing unit testing I was only concerned that when a user is trying to post one line from the statement with FEBAN this exit is called for all unprocessed lines from the same statement and I was not able to identify the line the user is actually posting (which, in my opinion, may prevent posting the whole bank statement if the data in one line is not consistent with the logic programmed in the exit ).

Which user exit in FM IDOC_INPUT_ORDERS to take IDOC segment E1EDP01 Plant

If the EDI inbound create order IDOC segment E1EDP01-WERKS is populated with plant code. Can some one please inform what user exit in FM IDOC_INPUT_ORDERS I need to modify to capture the plant code (E1EDP01-WERKS ) from IDOC and use to create and save that plant on a new order.
We saw that in "LVEDAF5N" other fields like E1EDP01-LPRIO are being moved from the incoming IDOC, but nothing for E1EDP01-WERKS.
We are hoping that we can use any of the SAPLVEDA exist ......EXIT_SAPLVEDA_XXX but not sure which one.....so if some one out there has some information please share ......

Try with the below exits.
EXIT_SAPLVEDA_004
EXIT_SAPLVEDA_005
Thanks,
Srinivas

User Exit with call up after document splitting in New GL.

Hello,
I am looking for a user exit which is called up after document splitting and before final posting to FI. We are implementing Ecc 6.0 and wish to change functional area on gl line item based on values in cost center. However, this change/redetermination of functional area also needs to be done on documents which have been split. Splitting is at profit center level.
Regards
Jayesh.

Hi Gordon,
Yes, by a little piece of ABAP.
I have created a Z table and configured by co.code and document type. Add a little bit of code in the badi FAGL_3KEH_DEFPRCTR.
Hope it helps.
Thanks,
Srini

User Exit / BADI available for PC00_M99_FPAYM - Create DME -Payment Medium?

Hi All,
We need to create a secure FTP process (SFTP) from SAP payroll system to the third party Finance syem to transfer Bank Files.
As of now, the Bank files generated using the above transaction is downloaded into local PC and manually uploaded in the Finance system.
However, we want to eliminate this manual intervention and send the generated Bank file directly to Finance system using SFTP.
Is there any User exit or BADI available to do this automation, once the user presses the Download button in PC00_M99_FPAYM program aftyer displaying the file?
If any of you have encountered similar requirement, please let me know how to proceed. Or any other suggestions to accomplish the required functionality?
Thanks & Regards,
Anshumita.

Here are the exits available in that TCode.
Enhancement
HRPCAL00                                User exit p/reports de clientes no menu cálculo folha pgto.
HRPY0001                                Definição da data início/fim p/os registros dados acumulação
Business Add-in
HR_PY_OUT_OF_SEQ                        Exits países p/rotina principal do cálculo folhas pagamento
HR_PY_ENQUEUE                           BAdI: atividades adicionais para empregados bloqueados
HR_PY_CLST_DISP                         PC_PAYRESULT: exit de país antes da exibição de uma tabela
HR_PY_AUTH_PU01                         Verificação de autorização própria do cliente PU01
HRPAY99_KTO                             Permite operações diferentes em relação a conta folha pgto.
HRPAY00_PRE_DME                         Exit p/programa prévio intercâmbio dados suporte magnético
HRPAY00_PAYMENTS                        Exit para a interface de transferência CL_HRPAY00_PAYMENTS
HRPAY00_ESS_PAYSLIP                     Verificar se comprovante remuneração só é acessível via ESS
HRPAY00_COL_DME_KEYS                    Chave de compactação para transferências coletivas
HRPAY00_COL_DME                         Motivo da operação na transferência coletiva
BADI_OCWB_REVERSAL                      Workbench off-cycle: excluir pagamento para estorno

User Exit to call program to create IDocs.

Similar Messages

Maybe you are looking for