While potential Supplier Registration in R12.1.x, when supplier wants to create a new Bank, Branch or Bank Account system gives error “Bank Does not exist”.
This problem will happen if Supplier selects “Account is used for Foreign Payments”
This issue can be resolved by Applying Patch “11058802:R12.IBY.B”. This is not documented on metalink in any published note
Following are Supply chain Management operations Strategies
Make to stock is the best strategy for standardized products that sell in high volume. Larger production batches keep manufacturing costs down, and having these products in inventory means that customer demand can be met quickly.
Make to order is the preferred strategy for customized products or products with infrequent demand. Companies following this strategy produce a shippable product only with a customer order in hand. This keeps inventory levels low while allowing for a wide range of product options.
Configure to order is a hybrid strategy in which a product is partially completed to a generic level and then finished when an order is received. This is the preferred strategy when there are many variations of the end product and you want to achieve low finished-goods inventory and shorter customer lead times than make to order can deliver.
Engineer to order, which shares many of the characteristics of make to order, is used in industries where complex products and services are created to unique customer specifications
|Strategy||When to Choose This Strategy||Beneﬁts|
|Make to stock||For standardized products selling in high volume||Low manufacturing costs; meeting customer demands quickly|
|Conﬁgure to order||For products requiring many variations||Customization; reduced inventory; improved service levels|
|Make to order||For customized products or products with infrequent demand||Low inventory levels; wide range of product options; simpliﬁed planning|
|Engineer to order||For complex products that meet unique customer needs||Enables response to specific customer requirements|
Now days I am reading a book “STRATEGIC SUPPLY CHAIN MANAGEMENT “ written by SHOSHANAH COHEN & JOSEPH ROUSSEL above is extract from that
I was working on one client site for AME setup with Purchase Requisition. I finished setup for AME transaction Type “Purchase Requisition Approval”. When requester was submitting requisition system initially shows that it’s in process but after one minute requester was getting notification “No approver found for Purchase Requisition”.
I checked from AME Test Workbench functionality by using transaction ID system was generating approval list as per setup. In other words everything was setup properly but still after submission user was getting error while submitting from Core Purchasing Form.
If user was completing this purchase requisition by using iProcurement Checkout functionality request was going for approval to supervisor as per setup.
After 2 days of working, found out one silly problem .guess what????????
Above diagram outlines the planned flow of an RFID Receipt. The huge potential of RFID is that data capture does not require user interaction or line of sight. So transaction can be processed without any manual user interaction with the system.
Here the action of a receiving dock worker driving through a doorway which is covered by an RFID reader will automatically trigger an ASN Receipt. Similar processes are possible for intra-warehouse moves, shipping, etc.
To make this work several components are required:
- Middle ware is required to interface with the RFID Reader hardware and to provide the appropriate filtering so that duplicate or erroneous reads are eliminated.
- The information from the read must be interpreted as a specific business event. This means that the ID of the tag must be resolved into some data on the system and based on the state of that data, the transaction to be processed can be deduced. For example, if you read an ID at a reader in Receiving, and that ID is associated with an LPN on an ASN that you have received from your supplier, then the transaction to be processed is an ASN Receipt of that LPN.
- The application must process that transaction using a API which does not require user input.
- Any results or exceptions must be processed and these made available (via the middle ware) to the light trees, buzzers, etc to single results to the user.
The above framework is currently being prototyped for possible inclusion in a future release.
Reference: – Oracle Apps World
1. Supply Chain Planning
MRP/Supply Chain Planning
Advanced Supply Chain Planning
Constraint and Inventory Optimization
Global Order Promising
Supply Chain Intelligence as an independent module
2. Order Management
Quoting & Proposals
– Project Manufacturing
– Flow Manufacturing
– Project Contracts
– Shop Floor Management
Mobile Supply Chain Apps
– Spares Management
– Advanced Scheduler
– Mobile Field Service
7. Maintenance Management
Enterprise Asset Management