Setup for Automatic Document Creation

1. Create an item with ASL enabled and List price = 1 ( any price) in pur tabbed region. 2. Assign the item to M1. 3. Create a supplier a1_adc_sup1 4. Create a Sourcing rule for the above supplier. ( Supply base - sourcing rule) 5. Ensure that "All org" is checked and 100 % allocation with rank 1 is entered. This will make the "Planning Active" check box ticked. 6. Assign the Sourcing rule to the item. Go to Supply Base - Assign Sourcing Rule and query on "Supplier Scheduling" Assignment set. ( Query is case sensitive). Insert a record for the above item. "Assigned to" must be "Item" and against the above item mention our sourcing rule. This establishes a relationship between item and supplier through Sourcing rule. 7. Make a check of this SR-ASR completion by creating a a req. The supplier info must populate in the req. 8. Create an Approved Supplier List for the above item. ( Nav. ( Supply Base - Appoved Supplier List) 9. Ensure that under the record details tabbed region, Global is set to "YES". 10. Create a BPA with an effective date under the terms button and approve it. Usually keep the amount limit and Minimum release as blank to facilitate an unlimited release. 11. Go to approved supplier list and under the suppliers choose our line and press Attributes button 12. Mention the above BPA under source documents with "Release Method" set to "Automatic Release" and save. 13. Create a requisition. When tabbed out of the item it will give a note saying that a BPA exists for this item. Accept it. This is as per selection in Purchasing option[Notify if Blanket PO exists] 14. Ensure that the BPA details are populated in the Source details tabbled region of the req. 15. The supplier details will also get populated from the sourcing rule in the Supplier region of the req. 16. This completes the ADC setup. 17. Complete the creation of the requisition and get it approved. Create another Requisition for the same item with different Need by date. 18. Run the concurrent program "Create Release" 19. Verify that a Release is created in the Purchase order summary [Query with View Releases enabled) with two lines for various need by dates. 20. Remove the entry of BPA in the Attributes button. Create another req and get it approved. Now run the Create Release and it will create the next BR. 21. Set the profile PO: Automatic Document sourcing = NO at the responsibility level. Create a Bid Quote and approve for the same item. Populate this Bid quote in the attributes button. Change the Release method to Release using Auto Create. Do step number 17. 22. We can observe the creation of Standard Purchase order for two lines. No need to run Create Release concurrent. 23. Now set the profile PO: Automatic Document sourcing = Yes. Now when you create

a req. you can observe that BPA is populated in the req and not Bid Quote. If PO:ADS = Yes, the system will first check for any valid BPA and if none found, then it will check for any valid Quote. Attribute button entry will be ignored. It will now need Create Release. 24. Set the Work flow attribute Send Auto Create to background = Y for the workflow PO Requisition Approval. Ensure the release method is set to Release using Auto Create, PO: Automatic Document sourcing = No and quote being populated in the attributes button. 25. Now upon completion of req approval, observe the workflow is struck in the background. Run the workflow background process for Process deferred = Yes and time out = No. A SPO will shoot out. 26. Repeat the above exercise for Send Auto Create to background = N. Observe a SPO coming out upon approval of req. Q1. Why does the create releases process not create a Release when we have run the CREATE RELEASES program against a Blanket Purchase Order whose EFFECTIVE DATES are in the future with a valid Sourcing Rule? [b]A:[/b] The CREATE RELEASE program must be run within the EFFECTIVE DATES of the Blanket Purchase Order. This is because the program verifies whether the SYSTEM DATE falls within the EFFECTIVE DATES, when looking for the Releases to be created. This is a standard functionality. Q2. Why cant we create a release of a blanket purchase order, When there exists a valid BPA and in the release form we pick the blanket PO from the list of values (LOV). Once selected, we cannot tab past that field and does not get any error messages. [b]A:[/b] Check for the invalid objects in the database. Invalid objects can prevent improper screen field action. Compile Invalid objects. Regenerate and recompile the forms and libraries. There are numerous packages and library handling code that the form utilizes. 3. When we try to run Requisition import after running a Min-Max planning request why is it that requisitions are created from Requisition import but no releases are created against blanket POs. [b]A: [/b]For Releases to get created automatically in the Requisition Import process: - Check for the profile option PO: Release During Requisition Import which should be set to 'Yes to create releases during requisition import. - 'Sourcing Rule' must have current date between 'effective date' and 'to date'. - Check that the requisition is sourced with the blanket, and the requisitions are approved as part of the Requisition Import process. - If the Encumbrance is ON, then the requisition will not get approved and will be in pre approved status and hence release will not get created. - Check the profile option MRP: Purchasing By Revision (If requisitions are coming from MRP) and INV: Purchasing By Revision (If requisitions are coming from INV). This

must be set according and should not be null. This profile option must be set to 'Yes' or 'No' according to the customers requirement. - Verify the table PO_REQUISITIONS_INTERFACE, column AUTOSOURCE_FLAG is Y. - Verify if this item has a blanket purchase agreement approved and it is not closed or cancelled. Q4. Why are we able to create releases against a Blanket Purchase Order even though the sum of amount of all the releases that have been created is equal to the amount on the Blanket Purchase Order? [b]A: [/b]Oracle Purchasing does not do any validation on the agreed amount limit on the Blanket until approval of the release. Q5. Why is it so that even though the Release is not approved, the amount against this release is on the blanket gets updated? [b]A: [/b]This is standard functionality. As soon as a release is created, the amount released on the blanket gets updated. In fact the amount released is not stored anywhere, system always calculates It whenever the blanket is queried. Q6. Why are the releases not getting generated automatically after the requisition import is run successfully for those requisitions, which are created from MRP? [b]A: [/b]Check that the Release Time Fence on the item in setup is defined. Creating a Release Time Fence on the item in setup solves the problem. The Release Time Fence on the item must fall within the established schedule in MRP. The Release method should be set to Automatic Release. Q7. Why is the Reqimport Automatically Creating Releases Although Profile PO: Release During ReqImport is set to No? [b]A: [/b]This might be because of the Incorrect WorkFlow attribute setting. Check the attribute "Is Automatic Creation Allowed" in the work flow process. This should set to N. Then the release is not created automatically Q8. Why is the amount released on the blanket PO is not updated and still includes the amount of the cancelled release after a release is cancelled? [b]A: [/b]Released amount of the blanket PO is not automatically updated if an invoice was previously matched and not cancelled before the release was cancelled. Q9. Why is the Create Releases program, PORELGEN is not creating any releases for requisitions, which are sourced to blanket agreements and have been generated from a template?

[b]A: [/b]The Source details on the requisition line have not been populated. The Create Releases program will only create a releases if the Source Document Number has been populated on the requisition line. When creating a requisition template, if you manually enter the item line there is no where to enter the blanket information. When the requisition is created from the template, the Source details on the requisition line are left blank so the Create Release program does not select the requisition. Instead of entering the lines manually while creating the template, use the Copy button, enter the type as Purchase Order and enter the blanket agreement number. The Source details will be correctly populated with the blanket agreement number and the requisition will be picked up by the Create Release program. Q10. Is the user allowed to modify quantity on distribution zone of an approved and reserved release? [b]A: [/b]Oracle Purchasing does not allow the user to modify the quantity on the distribution of an encumbered shipment nor does it allow creation of new distributions against encumbered shipments. Q11. Is the user allowed to delete an Incomplete Release? [b]A: [/b]Yes, The users are allowed to delete the incomplete releases in the application. Q12. Can we save and approve blanket PO releases without entering promised and need-by date? [b]A: [/b]If the item is either MRP/DRP, MPS/DRP or DRP planned item the promised date or need by date is mandatory and the user has to enter the date. If the item is not planned, then it is not mandatory. Q13. Can the users enter the P-Card number in the Enter Releases Form? [b]A: [/b]No. The users can not enter the P-Card number the core apps. A P-card may be specified in iProcurement, but is only a display only in Core Apps. We can see the PCard data if the profile option PO: Use P-card in Purchasing is set to YES. Q14. Can we cancel the releases if they are in 'incomplete' status? [b]A: [/b]Cancellation is an authorization provides to revert back the approved status. If we cancel the 'Incomplete' release we will loose the traceability of the document actions. Hence we will not be able to cancel an incomplete release. Q15. Does the Blanket Purchase Orders get Automatically closed After the Release is Fully Received and Invoiced?

[b]A: [/b][size=12]The Blanket Purchase Orders will not automatically close after the Release is fully received and invoiced. The roll-up of closed status for the Blanket Release Shipment happens to the Blanket Release Header and not to Blanket Purchase Order. This is the Standard Functionality. 1) What are primary and secondary price lists? Every order is associated to a price list as each item on the order must have a price. A price list contains basic list information and one or more pricing lines, pricing attributes, qualifiers, and secondary price lists. The price list that is primarily associated to an order is termed as Primary price list. The pricing engine uses a Secondary Price list if it cannot determine the price of the item ordered in the Primary price list. 2) What are picking rules? Picking rules define the sources and prioritization of sub inventories, lots, revisions and locators when the item is pick released by order management. They are user defined set of rules to define the priorities order management must use when picking items from finished goods inventory to ship to a customer. 3) Explain the Order Cycle? 1) Enter the Sales Order 2) Book the Sales Order(SO will not be processed until booked(Inventory confirmation)) 3) Launch Pick Release & Generate Pickslip Report and print. 4) Allocate and transaction Move Order (creates reservations, determines the source and transfers the inventory into the staging areas) 5) Ship Confirm (with Shipping and Bill of Ladding documents) and interface the Invoice to AR & decrement Inventory. 6) Close stops and trips on confirmation of receipt at Customers location. 7) Run workflow background process for order cycle completion. 4) What are trips and stops ? A trip is carrier specific and represent a unique instance of that carrier leaving the warehouse with deliveries having atleast two stops and carrying atleast a BOL document for every delivery. A stop is a point along the route of a trip that is due for pick-up or drop off. 5) What is a delivery leg ? A delivery leg consists of two stops where the delivery is picked up and finally dropped off. A delivery leg will have a bill of lading receipt which lists the goods that were signed over to the carrier. 6) When will the delivery details be back ordered ? If there is no material in Inventory during the Pick Confirm process when Pick Release is launched, the delivery details will be back ordered. Further during the ship confirm process, part quantities can be staged and or back ordered based on the carrier condition.

7) What are ship sets and arrival sets ? Ship sets are a group of lines which our customer has requested to be shipped together on the same date & time from the same warehouse. Arrival sets are a group of lines which our customer wishes to arrive at their ship-to location at the same time. What activities are performed during scheduling the order ? 1) Sales order lines ship and arrival dates are scheduled. 2) Reservation is placed if with in the res. Time fence. 3) Passes the demand to Inventory for consumption of the forecast. 4) Calculates the delivery lead time ship method set up by Inter location transit times. 9) Which item attributes will facilitate back to back ordering ? If Build in WIP and Assemble to Order attributes are enabled, the sales order will become eligible for create supplies, facilitating a back-to-back order. 10) What activity are completed when the Order entry line has a status Awaiting Shipping ? Awaiting shipping means that the sales order has undergone the workflow activities Scheduling the line and create supplies and it is ready for release in shipping execution. 11) Which rules will be invoked when Pick Release is launched ? Pick Release process will invoke Release rule, Release sequence rule and Pick Slip grouping rule. It will then allocate the material in Inventory using the Picking rule and generate pick slip grouping report for transaction of the material to the staging sub Inventory. 12) What will happen if we defer interface during ship confirm process ? Inventory will not be interfaced and it will not get decremented. We have to explicitly run a trip stop SRS concurrent for interfacing to inventory, relieve the reservation and to update the order line status. 13)What activities are performed during ship confirm process ? 1) Inventory gets decremented & Reservation is relieved. 2) Non-pick confirmed items gets back ordered. 3) Depending upon carrier condition, part items may get shipped, back ordered, staged or transferred to Cycle count in a combination of any or all these activities. 4) If shippable is checked, ship confirm is a pre-requisite for Invoicing. 14) Can we associate delivery lines to a existing delivery ? It is economical to associate delivery lines to the existing deliveries for utilizing the unused space ( weight ) of the carrier, provided all these lines have the trip stops as in an existing delivery. 15) Can we manually modify the price of a sales order line ? No. The pricing engine apply suitable modifiers associated with qualifiers to a sales order

line during the pricing phase activities of entering & booking and repricing. 16) When will the modifiers have incompatibility issues ? For a given phase and for a given level of incompatibility, the pricing engine will encounter incompatibility of multiple modifiers. It will allow only one modifier for the above combination and the exclusion is processed in the below mentioned order, till the incompatibility is resolved. 1) One exclusive group is allowed for a given phase of pricing. 2) The best price offered by any of the incompatible modifier will be chosen. 3) Modifier having the lowest precedence number rules supremacy over the other. 17) Can we apply discounts and surcharges for a same sales order line ? Yes. 1 Is it mandatory to use defaulting rules ? Defaulting rules simplify data entry and speed up order processing. It is not mandatory. 19) Can we book an order without entering any sales order lines ? Sales order line entry is not mandatory for booking an order. It can be accomplished with no entry in the lines tabbed region. 20) Can we part cancel a sales order line quantity after interfacing to shipping ? We can cancel a part of the sales order quantity by reducing the qty. in the lines region ( with reason) before confirm shipment. The changes will reflect in the detail and its associated delivery in shipping. These changes will also be reflected in Purchasing and WIP if Create Supplies were effected during order entry process.
SHIPPING EXECUTION FOR VARIOUS TYPES OF ITEM CONTROL.

1) ITEM WITH NO CONTROL. ship_item1 is defined and assigned in M1 with no control. A misc. receipt of 1000 q is received in Stores Sub Inventory. A Sales Order is made for Customer A.C. Network for 1200 Q. Upon booking, the SO progresses to Awaiting Shipping. When Pick Release is launched, the detail gets split into two One with 1000 q Staged / Pick Confirmed and the other back Ordered for 200 Q. SO line will remain intact with a status picked partial. When the carrier arrived, the shipping person found a dent in the corner of the carrier and it is not fit for carrying the entire 1000 q. The driver assures to send another small vehicle immediately to carry atleast 75 q. Click on the detail of 1000 q and mention the following Shipped qty : 900 Back Ordered qty : 25 Staged qty : 75

When ship confirming this detail, it splits into 3 details as mentioned above. If shipping rule does not defer the interface, Interface trip stop will run for the 900 q and this detail progresses to Shipped and then to finally Interfaced. Since these quantities are eligible for billing, SO line will now get split into two - first line with a status of Shipped for 900 q and the second line as picked partial. When Work Flow background concurrent is run for this process deferred line for the item type OM Order line, it gets closed and the SO data is packed and sent to the interface table of Receivables. This automatically kicks the ADS ( AutoInvoice Master) concurrent for the receivables Transaction source and Transaction type mentioned in our Order TT. It in turn runs the Autoinvoice Import, creating the Commercial Invoice under the navigation Receivables Transactions Transactions for further processing. The staged qty is assumed to be repacked and kept ready for loading into the small vehicle expected shortly. A new delivery is auto created and assigned to this 75 q. This is now ready for ship confirm process. The back ordered qty is removed from the original consignment and kept on the floor of staging. Its delivery is unassigned. It needs Pick releasing. PR process does two activities. Creating a MO and allocate, print Pick slip report and transact the MO and Cleaning, weighing and making it ready for Ship confirm. PR this back ordered detail. Since the first activity is already completed, PR process is ensuring the second activity and the status progresses to Staged/Pick Confirmed for 25 q. Mention shipped qty as 20 and back ordered qty as 2 in the detail line and proceed to ship confirm the delivery. The balance 3 qty are considered as unspecified qty. In the ship confirm rule, mention Unspecified qty to be Staged , This action will result in splitting of this line into three : 20 as Interfaced, 2 as back ordered and 3 as staged. SO

line with further split with 20 as shipped ( Invoice eligible) as the second line and the balance as Picked partial. All shipped details in Shiping Transactions will reflect as Picked SO lines in Order Entry and are eligible for interfacing to inventory. Upon running ITS concurrent, SO line progresses to its last status of Shipped and shipping transaction will reflect as Interfaced 2) ITEM WITH SERIAL GENERATION AT RECEIPT. Define and assign ship_item2 with Serial generation at receipt. Make a misc. receipt for 100 q with serial nos. sno_101 to sno_200. Set Allocate Serial number = No in Organisation parameters ( 3rd tabbed region). Book a SO for 50 q and launch PR process with auto allocate check box enabled in M1 shipping parameter. The concurrent Pick selection list generation will fail and the allocation process will fail to allocate SNOs. The detail gets Released to warehouse. Since Serial numbers are not a constituent of Picking rule, the org param setting of No sno allocation, demands a manual allocation. The business process is as follows : The Monitors produced in WIP is received in FGS with a serial number. The company has a policy of making a final inspection during PRing as the item may be residing in FGS for long. This inspection and testing may result in rejection / rework on some of the monitors, and so there may be breaks in the contiguous allocation of serial numbers. To facilitate manual sno allocation, Allocate Serial number = NO will allocate the sub inventory automatically ( FIFO / LIFO) and will demand a manual allocation of serial numbers in transact Move Orders form under View / Update allocations. It is then followed by manual Pick Confirm process by transact MO, and the detail progresses to Staged / Pick Confirmed If Allocate sno is set to YES User defined in org parameters, even the Sub Inventory has to be allocated manually. A setting of YES will allocate everything automatically. 3) ITEM WITH LOT CONTROL

Lot control is superior to serial control. Since Lot depicts the characteristics of an item ( say chemical / physical properties like 75% concentration, ergonomic design etc.,) certain lots can be reserved for priority customers by Customer Service Representatives at Sales order level. Serial numbers are used as identifiers of a specific item for the purpose of tracking and warranty and so all serial numbers are supposed to exhibit the same properties. Define and assign ship_item3 with Lot control as Full Control. Make a misc. receipt of 100 each for lot numbers lot1 and lot2. Book a sales order for 150 q. CSR can now reserve a specific lot as part of marketing promotion. Let us say he assures 35 q of lot2 for a specific customer. This is done under Tools Scheduling Reservation details. Here specify the lot and the qty. This is considered as high level reservation. Upon PRing this detail, the detail splits into three : 35 q of lot2, 100 q of lot1 ( FIFO) and the balance 15 q in lot2. Here the customer is assured 35 q of lot2 at the SO level. This facility of high level reservation is not available of other item controls.

4) ITEM WITH SERIAL GENERATION AT SALES ORDER ISSUE. This is a case where items are mass produced and stores in FGS. Actual warranty starts upon powering / usage start and so they will be allocated serial numbers during ship confirm process. Define an item with Serial gen at SO issue. Make a misc. receipt of 100 q. SNO will not be asked during inventory receipts. Book a SO for 50 q and PR the items. Detail gets a status Staged / Pick Confirmed. Try to Ship confirm. It will flash a message stating that the items do not satisfy inventory controls and the delivery gets unassigned. SNOs need to be assigned before SC process. Auto create delivery for this staged qty. Remove any qty in shipped qty. Serial numbers will be greyed out in Tools Serial numbers. Mention a qty of say 30 in shipped qty and allocate serial numbers in Tools Serial numbers. Normally sno allocation will behave like a pre-defined during issue. But here it will be analogous to at-receipt as there are no snos existing. Upon ship confirmation, we can notice the balance qty of 20 getting back ordered.

These serialized items will create an instance for every serial item in the installed base for recording after sales customer service, if any and for knowledge base creation in CRM module. 5) LOCATOR CONTROLLED STAGING When the destination sub inventory is locator controlled, PR will fail to allocate destination. This is the case where precision / sophisticated items must be kept on a locator in the staging area for proper material handling. Move order normally allocates the source sub inventory ( FIFO / LIFO in picking rules) Since the destination staging is locator controlled, Item Transaction defaults have to be defined before PRing. Create a staging sub inventory with pre-specified locator control. Create locators 1.1.1 , 2.2.2 and 3.3.3. Mention this as the staging sub inventory in shipping parameters. Upon PRing any detail. it will fail to allocate. Specify ITD for the sub inventory and locator 2.2.2. in nav : setup transactions Item Transaction defauls. if you again PR, it will be successful. ITD needs to be specified for every salable items, if destination staging is locator controlled. 6) ITEMS WITH HOLDS If a hold or a credit check is placed on a item in OE, it will not allow to PR the detail in shipping. The status remains in Ready to release even after PRing. Only upon releasing the hold, the detail becomes eligible for pick release. A credit check hold can be placed during PRing, Packing or SCing.