Validation Template for Processing Constraints in Oracle OM

-


Order Management provides you the ability to define your own validation conditions by the use of validation templates. A validation template names a condition and defines the semantics of how to validate that condition. Validation templates can be used in the processing constraints framework to specify the constraining conditions for a given constraint.

These conditions are based on:
• Where the entity is in its workflow
• The state of attributes on an entity
• Any other validation condition that cannot be modeled using the above methods

API based validation templates are not available if constrained entity is different from the entity for which the validation template has been defined (or the Validation templates are not available even if the record set being used is anything other than the primary key record set).

For Example, API based Validation template Pick Released has been set up for entity Order Line. If you set up a constraint for attribute ShipTo on Order Line, the validation template Pick Released is available but for a constraint on attribute ShipTo on Order Header, Pick Released will not be available.

For attribute Ship To on Order Line, if the constraint condition uses any record set (ATO Configuration, for example) other than the primary key record set Order Line, the validation template Pick Released will not be available.

Define a validation template:


Validation Types
Select the Validation Type to be performed by the condition. Select from:
WF: (validation is based on the workflow status of this entity):
•        Select the Activity for the condition
•        Select the Activity Status for the condition. Select from: Active, Complete, Error, Notified, and suspended
•        Select the activity Result for the condition
•        Save your work
API (validation is completed through an Application Program Interface):
•        Select the PL/SQL Package you wish to interface with the constraint condition
•        Enter the Procedure name of the API
•        Save your work
TBL (validation is based on the values of database columns on this entity):
•        Select the Attribute Column name on the entity for the constraint condition
•        Select the Validation Operation for the constraint condition. Select from: = (Equal To), <> (Not Equal To), Is NULL, Is Not NULL
•        Select the Value String you want to validate against the value of the column

Comments

Post a Comment

Popular posts from this blog

Oracle Purchasing Module Step by Step in R12

-
Image
PURCHASING  All the Purchasing related activity information will be declared in Purchasing              Procure 2 Pay Cycle : Requisition à RFQ à Quotation à Quotation Analysis à Purchasing à Receiving à Invoice  à  Payment à Reconciliation PO-Integration :  PO  is integrated by GL, AP, I Supplier, Procurement, and Project Accounting  PO  Responsibility             Step1: Define  PO  Responsibility                         Nav: System administrator à Security à Responsibility à Define             Step2: Assign  PO  options to the PO Responsibility                 ...
Read more

Sub Ledger Accounting SLA (Complete Functional Information)

-
Image
SubLegder Accounting in R12 SLA Part -1 In these article, we will explore the very basics of SLA and why it exists. Firstly, what exactly does SLA do? SLA is a module which now sits between the SubLedgers like AP/AR etc and the General Ledger. Have a look at this diagram below.  As you will notice, SLA can act as a mediator between the subledgers and Oracle General Ledger. Before we progress, some terminologies of R12 must be revisited. In 11i we had set of books, and in R12 we call them Ledgers. Likewise in R12 we also have secondary ledgers and reporting ledgers. Hence from 11i perspective think of Ledger as Set of Books. As for Subledger, a Subledger is nothing but a module like AP/AR/PO/Inventory etc. In the diagram below, the second scenario is explained whereby let's say that payables module generates a charge account segment combination for an invoice distribution line as A.B.C.D. In such case, if SLA module is not customized, then the very same A.B.C.D ...
Read more

Difference between ATO and PTO in oracle apps

-
Difference between ATO and PTO in oracle apps 1) MAKE TO ORDER: This is based on Customer specification, you make the product and supply it to them. This is applicable for Engineering items or any Product which you can make based on Customer order Example: Engineering Items 2) ASSEMBLE TO ORDER: This is you have items in parts and it needs to be assembled according to customer requirements For example you have Laptop coming with standard configuration of 160GB Hard disk and 1 GB RAM. But there are customer orders coming in asking for 200GB Hard Disk and 2 GB RAM and if you can assemble them to suit Customer Requirement 3) CONFIGURE TO ORDER: This is Configuring the Product itself to suit Customer requirements Example. The Thread Manufacturing unit Machineries are configured. I have seen Laxmi Machine Works in INDIA which manufactures textile Machineries configure the machineries based on No.of spindles 4) PICK TO ORDER: This is same as Computer Example in ATO. But the  differenc...
Read more