Transaction CREPFP
Introduction
This transaction is used to create, maintain and release a program, fees for the program and limits of the program.
Detailed information about program can be found in the Maintain Program article.
This transaction acts as a one stop shop to set up the Program, the Fee conditions and the Limits for a program. The separate Static Data transactions for each can also be used if desired.
CREPFP uses the Maker/Checker Release process, which means the user entering the data has to set the transaction to done once all information including Program, fees and limits are complete. And another user must login and check the data and release it, which can then trigger a message for an external system that is connected to the product to further proceed.
This process will also set the status of the Program details to Waiting, Pending and Active accordingly.
Status Handling:
Pending: when the user is still preparing the data
Waiting: when the entry is signed by the maker and is waiting to be released.
Active: when the entry is released and the data is sent to external front end system such as RIVO.
Process
When starting the transaction, the “Search Panel” is displayed. The buyer and/or program number can be entered or selection field can be left empty. The programs which meets the selection criteria, or all programs (in case of empty selection field) are displayed in the selection list.
The + icon on the top menu bar will navigate the user to Adding Program where a new program can be created. Once the program is created, the user is returned to the CREPFP transaction and status of the Program is set to “Pending”.
The “Program Fee Conditions” grid displays the fee conditions associated to the program.
The user can add fees for the selected program by clicking the +- icon on the top right corner of the grid which will start the Add Condition transaction with condition set as “Program” and Program No. field is defaulted to the selected program.
The “Program Limit” grid displays the limit associated to the program.
The user can add limits for the selected program by clicking the +- icon on the top right corner of the grid which will start the Adding a Limit transaction with Type as “Liability per Program” and Program No. field is defaulted to the selected program.
Once all the three details, Program, Fees & Limits of the program is saved, the user can sign the process mentioning all relevant information is now updated using tick icon. This sets the status of the Program to “Waiting” and is now available for a checker to release the program details.
A different user must then login and use the same icon to check and release the transaction. Upon release, it will generate and send the message to the external connected interface such as RIVO. The sent documents will be listed in panel Fees & Limit, under the “Send Requests of Program” grid. The “Send Requests of Program” displays the sent requests of the program including details like the Medium, External Key, Document name, creation date and the releaser. Clicking the view Icon will display the XML file.
The Transaction 4-Eye Principle Release (SPTREL -Release Pending Items) can also be used to view and release any entries.
Warning such as "Entry is waiting to be released" will be displayed even if Individual entries eg . Limit , fees are waiting for a 4-eye static data release.
Steps to create a program
1.Create a party record with buyer as an option .
2.Launch DBIPFP to Maintain a Program .
3.Provide the necessary details like the party created , Unique Program number and desired finance details .
4.Record saved successfully . Once saved it will moved to release .Status will be denoted as Pending
5.Record is released and Processed in SPTSEL : Selecting pending items
6.Once executed , status will be moved to active .
7.Launch CREPFP , your Program will be listed here. You can select the program and edit the limits and fees .
8.Release these details using another user .Once done an Interface PFP xml will be created successfully .
Follow the below gif for detailed process :
Comments
0 comments
Please sign in to leave a comment.