Examples with "payment process request flow" and their translation in Japans
We konden deze vermelding niet vinden. Er worden benaderende resultaten weergegeven. Controleer je spelling of stel voor deze term aan het woordenboek toe te voegen.
Payment Process Request Flow
支払プロセス要求フロー
Payment Process Request Flow (F3)
支払処理要求フロー(F3)
The source product submits a Payment Process Request to Oracle Payments to process payments for its selected documents. The diagram below shows the steps performed when a Payment Process Request Flow (F3) is submitted to Oracle Payments.
Document Selection (F2) The source product performs a document selection process. The selected documents are grouped into a Payment Process Request. Note: Flows F2 and F3 are tightly linked. The Document Selection Flow (F2) can be scheduled. The steps in the Payment Process Request Flow (F3) happen automatically upon completion of Flow F2.
Payment Instruction Creation (F8) Oracle Payments processes payments within each Payment Process Request and groups them according to their internal bank accounts, payment profiles, and other grouping rules to create payment instructions. This processing may result in Payment Process Requests being split into different payment instructions or combined together into payment instructions. Note: Flows F6 and F7 complete the creation of a payment process request. Flows F8 to F12 and F15 to F17 occur in the context of a payment instruction.
Read Documents in Request The source product reads all the documents that it built into the Payment Process Request in the Document Selection Flow (F2).
Oracle Payments performs validation on all data received in the Payment Process Request. This validation process may result in failures when documents payable do not pass the validation checks. All steps performed by Oracle Payments in the Document Validation Flow are part of the Build Payments program. For information on the Build Payments program, see Build Payments Program.
Account/Profile Assignment (F4) This flow assigns internal bank accounts, which are the deploying company's bank accounts, and payment process profiles to documents payable within the Payment Process Request. Oracle Payments automatically assigns these values when possible. It also provides a user interface for users to perform these functions if needed.
Payment Process Request (F3) The Payment Process Request is submitted to Oracle Payments for processing. Note: Flows F3 to F7 occur in the context of a Payment Process Request.
Review/Modify Process (F7) Implementers may set up Oracle Payments, or specific payment process requests, to stop the payment process for review after proposed payments are created and can review the proposed payments and possibly choose not to make some payments, before allowing the payment process to proceed. The next step in the funds disbursement payment flow varies, depending on the actions you take in this process. If modifications are made, the process returns to Payment Creation (F6), to be revalidated.
Stop Process for Review Perform no Automatic Rejections: If the system option has this setting, Oracle Payments does not automatically reject any payments. Instead, user intervention is required to review and take action on the failed payments. Update Payment Status: For any payments marked as having validation errors, the payment status is set to Failed Validation. Accept all Other Payments and Flag them as Validated: Oracle Payments sets the status for all payments that passed validation to Created. Update Request Status: Oracle Payments updates the status of the Payment Process Request to Payment Validation Errors - Pending Review. This status prevents the request from being selected for further payment processing. You can then take actions in the Review/Modify Process Flow (F7) to cancel or correct payments with errors.
Any Documents Missing Information? Once the defaulting process is complete for each document in the Payment Process Request, Oracle Payments determines if any documents are missing the required information. (No). If all documents are complete, then the flow is complete and the payment process proceeds to the document validation phase (F5).
The Account/Profile Assignment Flow assigns required payment information to the Payment Process Request. This information is needed for further payment processing, including validations in the Document Validation Flow. All steps in this flow are performed as part of the Build Payments program until you take action in the Complete Document Assignments page (C5).
Er worden alleen voorbeelden gegeven om u te helpen het woord of de woordcombinatie waarop u hebt gezocht, te vertalen. Deze worden niet door ons geselecteerd of gevalideerd en kunnen ongepaste taal bevatten. Wij vragen u melding te maken van voorbeelden die dienen te worden aangepast of verwijderd. Vertalingen met grof of informeel taalgebruik worden meestal rood of oranje gemarkeerd.