Unable To Approve Blanket Purchase Agreement In Oracle Apps
If you want to specify the authorization assignments for the purchasing department described in the Authorization Rules document (See: Define Authorization Rules), you can start with the Senior Buyer topic. Assuming that senior Buyer is able to approve all types of documents, you can configure the control assignments as follows: If I make a framework contract without a globlale option enabled, I do not have this kind of problem. The main differences between order authorization procedures and main authorization procedures (one applies to orders and the other to requirements) are as follows: the workflow process for change orders uses the same reissue rules already defined in the purchase to determine whether a document needs to be relearned. Different rehabilitation rules are used depending on the type of document: standard order, planned order, framework contract, contractual sales contract, framework release and date release. See: Rules for re-generation of documents. If you have not configured the timeout function, the authorization workflow does not exceed the time. He is just waiting to get an answer from this genealogical. If Junior Buyer can allow shares (and not other types of documents) based on the eligibility criteria you specified in the Define Authorization Rules document, rearrange the control assignments of this position as follows: Let me let me point out my problem. I`m trying to create a purchase contract (Order Purchase), but in a global way.
I mean, I`m ticking the global option. When I am finished, I accept the order and will receive an order ID. Next, I try to create a version from the Previous Blanket Purchase order. If I insert the PO ID I received earlier, the system gives me an error (PO_NUM invalid). 5. In OU1, we reviewed and tried to approve the approved GBPA. But that`s not okay. 4. Create GBPA and try to approve OU1. It was approved for revision 0. But it is not possible to approve it at OU2. You can use the Builder workflow to change the percentage tolerances.
Some of the re-equipment rules used by the workflow determine the percentage change in a price, quantity, or document amount that requires new viennalization. Workflow represents these tolerances as percentages as attributes that you can change. For example, you can change the value of an attribute from the unit price tolerance from 0 to the unit value tolerance from 20. This means that if the unit price is increased or reduced by less than 20%, the document will be automatically relearned by the change order workflow. MRO buyers should be able to approve each type of document for MRO item categories with a maximum value of $10,000. Write the authorization assignments as follows: You are not creating a share for a global sales contract. Instead, create a regular (standard) order for the same supplier and item, and you can see that this document links to the global BPA. There are some very good documents on Metalink.
We have completed the following configurations in R12.2.7 to approve gbpa. If there is no authorization group associated with a particular type of document for a particular job or position, staff assigned to that organization or position cannot approve such documents. If the “Create Documents” workflow creates a sharing document for a “local” framework contract from an approved request, this workflow creates a default command. Global EPS has been designed for multiple business units to share negotiated prices, but even in facilities or individuals, suppliers prefer a unique order number (instead of the same BPA number – exit document). We also found that AP had fewer errors made on invoices. I don`t know what I`m doing wrong or I need to set something up for the system to work with a global framework contract….