Generating/Trigerring IDoc PEXR 2001/2 through F110?

Hi Community:
Need help on IDoc/Payment Instruction File/Payment Acknowledgment to and from an external non-SAP system
Scenario 1:
We have SAP system and an external non-SAP payment system, say X.
SAP will send a payment instruction file to X
X will authorize the bank to release payments to vendors.
For this, the X needs info on the valid payment methods that can be processed by it (along with the amount to be paid).
Now, as per my understanding we need IDoc PEXR 2001/2002, message type PAYEXT for acheiving this ( I suspect that F110 will be involved in the process). I guess F110 will (or should) trigger an IDoc that will be sent to X. This IDoc will be a payment instruction file.
Question 1:
How can I trigger the IDoc from SAP for sending payment instruction file to X
I guess this be achieved though F110. Not sure how.
If not F110, then how?
I read somewhere in the forum to use RFFOALE1 program. Can this be used? If yes, How?
Scenario 2:
Once the bank pays the vendors, it will send an acknowledgement to X and the same will be sent back to SAP from X. (Acknowledgement of payments made)
Question 2:
How will SAP receive the acknowledgement from X.
Which IDoc will be used? How/where to configure?
Helpful answers will be rewarded
Vj
Happy Diwali

Hi
If you were to use payment instruction IDOC, SAP Standard program should be RFFOEDI1, which you need to configure in FBZP payment configuration (I think it should be under payment method at country) and set up a variant to generate IDOC, which again needs to be specified in F110 parameter.
If you are using IDOC solution and need to provide solution regarding the banks' acknowledgement or confirmation against the payment instruction sent, we developed a bespoke solutionwith bespoke table to link up the confirrmation from bank to instruction since, as far as I know, there is no standard solution in this way.
However, in ECC6.0, you may probaly as well look into the use of Payment Medium Workbench to produce payment media file via Bank communication management module. in BCM, Payment and Batch Monitor functionality can provide the status of payment batch by interfacing back the acknowledgement as well as confirmation or rejection by updating the status of payment batch.
Hope that this helps
taro

Similar Messages

IDOC Output for Payment Run through F110

Gurus,
I am trying to generate IDOCS for the payment run through F110 transaction. I have setup the following but still unable to generate the IDOCS.
- Bank partner setup with IDOC PEXR2001 and message PAYEXT.
- House bank configuration.
Can anyone help me with the complete set of instructions to generate the idocs?
Thanks in advance,
Rishi

Hi
Have you done House Bank Configurations (FI12) and APP settings (FBZP)
Are you using workflow concepts in this Scenario.
Please check these 2 settings may be problem with these settings.
Thanks
Chandra

Incoming payments through f110 ?

HI,
Can one of you please give some info. On the following..
F110 .. We can also use for incoming payments. Can you please let me know when exactly we will execute incoming payments through f110 ?
For vendor it makes sense that it will collect the all pending open invoices and will generate a payment document including check printing(or whatever the payment method) to vendor.
Step 1. Create vendor invoices
Step 2. Run F110
Step 3. F110 selects pending invoices and generates payment documents
Step 4. depending on payment method It will allow us to pay the money to Vendor through cheque/ cash/ etc.,
I gues incoming payments is for receivables from customer, if so then what f110 does for incoming payments..
I feel if we know that customer deposited the money in bank (through bank statement) then we can run f110 for the open documents is it correct ? Or any other options.. Let me know step by step process like vendors
Step 1. Create Customer invoices
Step 2.
Step 3.
Regards
Ravinagh Boni

Ravi,
F110 can be used for incoming payments as well.It is not a common practice across all businesses. This process is called as ACH direct debit. In simple terms it is pulling money directly from customer bank account.Required things;
1. A payment method for Incoming payments, Payment medium program used for this payment method is RFFOEDI1
2. Banking information in customer master.
To explain it further:
1. Post invoice to customer
2. Run f110 to clear the invoice by inserting customer number in the parameters tab
3. Payment program creates an IDOC with all requirement information for the banks to process payments
4. if the bank accepts IDOC send idoc's to bank, if not process data in EDI translator and send the file to bank in aceptable format
5. Bank processes the payments and sends the clearing transactions as a bank statement
6. When EBS is processed main bank account will be updated.
I hope this helps,

Funds trf through F110

Hi,
The clients bank has provided an online payment service through IDOC. The payments have to be made through F110. Now the client wants to use this facility to make book transfers (between their own accounts with in the same bank).
Presently they are doing some manual postings. But payments ahve to be generated through F110 for generating an IDOC.
Can you please advise me how to make book transfers through F110. Pls let me know if more info/ clarity is required.
Thanks
Rekha

Hi Srikanth,
Our client is banking with say "ABC bank". And the client maintains about 8-10 different accounts with this bank. And they transfer funds from one account to another account frequently. they want to make the funds transfer through APP.
when we run f110, all the unpaid invoices of the vendor are selected in the APP. But in this case, we are not making any payment to a vendor. But in this case there are no third party involved, nor any open vendor line item to select for payment.
As per my knowledge, it si not possible to make funds transfer internally, through F110. Please give your inputs/

Automatic payment run through F110

Hi Everyone,
During the aotumatic payment run via F110, after creating the proposals when i am trying to display the proposal, it is giving an error message that " Company Code XY12 / XY12 does not appearin proposal 08.07.2011 AB00; correct "
But I already set company code XY12 , in the company code in the parameter tab. I ahve also set there payment methods and next payment date. Please help.

Hi
After you get the mesage
Carried out Automatic Payment Run through F110
Posting orders: 2 generated, 0 completed
You need to refersh data by pressing Status or Pressing Enter.
Regards
Venkat

Inter company cheque payment through F110

Hi all,
what customization needs for intercompany payments through F110.
i customized settings, but cheques are not generated.
can any one kindly tell me details of this settings.
points will be awarded.
Rgds,
Soma

Hi,
In FBZP -All Company Code, check sending & paying company code. Check intercompany Clearing accounts, and in f110, Parameters screen give the company codes for which you want to make the payment.
Also check whether the entries are generated before cheque printing
This should solve your problem
Reply if it you have the same problem.
Thanks,
Sujai Chandran

Generate outbound idoc for Customer Master

Hi Developers,
I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
Thanks in advance for helping.
Regards,
Gajendra

Hi,
If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
If you want to send the idocs automatically, then you will to configure some program.
Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
Transaction SPRO
SAP Customizing Implementation Guide -->
SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
Take a look at this thread.
Re: automatic Idoc outbound
Regards,
Ravi
Note : Please mark the helpful answers
Message was edited by: Ravikumar Allampallam

Direct Deposit Through F110

Hi,
How can we do direct Deposit through F110.i got this issue.But i didnot get their requirement.Give me some suggestion.
Thanks
Sap Guru

Hello
Direct deposits, say for example employees can be possible through F110 if the Payroll accounting is also active.
Even otherwise, a direct deposit is possible, if the out put is data medium file, which can generated and uploaded to the bank. The bank would make the direct deposits.
Reg
assign points if possible

Generate DELVRY Idoc when Post goods issue is done in SAP

I need to generate an Idoc when post goods issue is done in SAP (outbound to SAP) .I understood that I can do this using the message control .The message type DESADV with the process code DELV will support this.
But I didnt understand how to trigger the Idoc.In the current scenario our Company is doing the post goods issue in SAP for the in three different ways.
1.Manually doing the post goods issue through the transaction VL02N
2. an Inbound Interface (using Idoc) which will do Post goods Issue in SAP
3.Another Interface using BAPI, which will, do post goods issue in SAP
I have to run my outbound interface when the post goods issue is done by all the above three ways. Can any one help me out in this?

You have to configure the output first .
You can use output type LAVA ( avaialble in Std SAP ) .
( Tcode is NACE , Select Application V2 -> Outputtypes ).
( Create condition records suitable to generate an output)
Next is ALE.
Setup a distribution Model ( for DESADV ) and all other setup for ALE i.e. Distribute Dist. Model / Generate Partner Profile .
In the Partner profile in WE20 select your partner system. Double CLick on Outbound Message DESADV ( this wd be there after you generate partner profile , if not add it here in outbound ) . On this screen goto tab MESSAGE CONTROL .
Application - V2
Message Type - LAVA
Process Code - DELV.
Now you are ready to go. The moment a PGI is done in any form an output LAVA would be proposed and processed using process code DELV.
Cheers.

EDI Output type generating multiple IDOCs

Hi All,
For one of the Business requirement we have created a Delivery EDI output type and output type is processed via Report RSNAST00 in a batch job.
The delivery document shows only one output type prcossed still, mutiple idocs are being sent out for this Delivery.
RSEOUT00 is being used to process outbound IDOC.
Any pointers toward this abnormal behavior shall be helpful.
BR,
Anshul
PS - We havent implemented change Pointers

Okay, so you have one output record in the delivery document generating multiple IDocs.
Compare the control records of the generated IDocs. Do they have the same Basic Type, Message Type and recipient Partner Number?
If yes,
1. Check for multiple background jobs running RSEOUT00 at the same time. Seems unlikely, but this is easy to check and eliminate as a possible cause.
2. Step through the program RSEOUT00 as it generates the output type for one delivery document. Perhaps something is happening in a user exit that inadvertently results in replication of the IDoc.
Otherwise, the process code that gets executed by the output type in the delivery document is, for some reason, generating additional output. I donu2019t know of any standard output process code that does this, but it could be deliberate (by design). If you are sure that it should NOT happen, then step through the code and look for a mis-behaving user exit.
Regards,
zKen

Trigerring idoc in idoc2file scenario

Hi
how the idoc is triggered in scenario idoc2file,in which idoc is on sender side and file on reciever side.
regards
prasad

Hi,
Once you configured the ALE settings, ask your functional people to generate the idoc. then goto we02 take the IDOC number fom there and paste it in WE19 ( IDOC Test Tool)
And then u can send the IDOC from R/3 to XI in this way
ALE Settings
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Reposting IDocs instead of Recreating - For Testing
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
IDOCXI-File Scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
REgards
Seshagiri

F150 Generate SAP idoc

Hi,
I have a problem for my test, when i run F110 with my program run date and my identification feature.
When i run printout. In Generate SAP IDoc , the printer is lock to $H208.
Where can i custom this parameter please?
Thanks.

Hi,
I have a problem for my test, when i run F110 with my program run date and my identification feature.
When i run printout. In Generate SAP IDoc , the printer is lock to $H208.
Where can i custom this parameter please?
Thanks.

Necessary configurations required to generate an IDOC

Hi Friends,
I want to know the necessary configuration that has to be done , inorder to generate an IDOC when a particular record is saved.
for example when I tried to change the QTY in Me22(PO), an IDOC, orders05 need tobe generated, which is not getting generated. Please let me know the configurations needed to generate an IDOC.
Thnaks in Advance,
Meghna.

Hi,
you need to call the outbound processing program for IDOC,
The system generates an IDoc of type ORDERS01, which is not yet transferred to the port (output mode Collect IDocs) for Tcode ME11.
Similarly you need to call the IDOC processing Function Module in User Exit of Tcode ME22
Refer
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a60c8507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f2/660b378350c976e10000009b38f839/frameset.htm
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
Thanks
Swarup

Exit in iw31 for generating IORDER IDOC

Hi,
We are trying to generate the IORDER01 IDoc for PM orders through transaction iw31. I need exit name where i can write code for generating idoc. Exit should be triggered <b>after save</b> as i need to pass the following data - order id and operation details.
I tried exit - FUNCTION EXIT_SAPLCOIH_016 but it doesnt work
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(CAUFVD_IMP) LIKE CAUFVD STRUCTURE CAUFVD
*"             VALUE(AFVGD_IMP) LIKE AFVGD STRUCTURE AFVGD
*"             VALUE(ACTYP) LIKE TC10-TRTYP
INCLUDE ZXWOCU13.
ENDFUNCTION.
Please suggest correct exit name. Thanks in advance.
Sonali

Thanks Sajan.
Exit 031 triggers after save but at that point the order id(aufnr) is not generated. The system generated order number is also to be passed to the idoc so i need exit after FM - CO_ZV_ORDER_POST (include LCOIHF2V) is triggered.
i could not find exit after this FM. Apart from exit can we use any other method ? i've not worked on badi so not sure which method of IWO1_ORDER_BADI would work.
Any help on this is appreciated. Thanks a lot.
Sonali

How to create an extension for generated type idoc

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

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

Generating/Trigerring IDoc PEXR 2001/2 through F110?

Similar Messages

Maybe you are looking for