Here is a little twister on Oracle sequence object.
Typically, when we invoke a nextval operation on a sequence object, the current value of the sequence is incremented by 1 and the incremented value is returned. Our assumption here is that this happens irrespective of when and where the nextval operation is invoked.
Turns out that we may be way wrong in our assumptions...
Let us say we have a sequence object named DUMMY_S and its current value is 1.
What would we expect to happen when we execute the following SQL statement?
For those of us who are mulling over the possibility of copying large sets of BOMs and Routings across inventory organizations, can consider using the following standard Oracle APIs:
The following is the outline for developing a bulk API utility that cancreate/register/approve isupplier user accounts. The utility will also be able to assign responsibility access to supplier user accounts, attach securing attributes including supplier, supplier sites to the user accounts. The securing attributes can contain multiple supplier site information. This utility can be developed in PL/SQL and registered to run as a concurrent program in Oracle eBusiness Suite.
Have we ever wondered if there is a better way to document design/program logic for a large scale application?
Typically we would consider using generic text based Pseudo-code techniques to lay out the flows. If the pseudo-code burgeons as time passes by, it becomes increasingly difficult to understand the flow from the myriad of statements that make up the pseudo-code. Indentation of statements can only help for small to medium scale designs. For large scale designs, it might be worthwhile to create or develop our own standards based XML language for documenting pseudo-code.
The SOA Design Patterns site (and book) has an interesting chapter on the topic of schema centralization. The recommended solution is essentially the pattern used in AIA.
1. Establish your service inventory using a top-down business process model driven approach.
2. Identify the Enterprise Business Objects (EBO) and Enterprise Business Messages (EBM).
3. Create the EBO Schema canonical definitions using the industry standards.
It is a well known fact that the following APIs are used in Oracle eBusiness Suite to control the submission of concurrent requests:
This API is used to submit the concurrent request and get the request id for the submission