Oracle-OM-iStore-iPayment

WHAT IS IPAYMENT? Oracle iPayment is a complete electronic payment processing solution designed for application developers, systems integrators and enterprises that need to "payment-enable" new or existing Internet or client/server applications. Oracle iPayment supports multiple payment processing systems operating simultaneously and provides a powerful, business rulesdriven routing system that gives businesses and merchants full control over transaction processing. iPayment provides payment instrument registration APIs for registering payment instruments such as credit cards, bank accounts, and purchase cards. It also provides payment transaction APIs that can perform credit card and purchase card operations such as authorization, capture, and bank account transfer operations. Risk evaluation APIs are provided to perform risk analysis. iPayment integrates with Oracle Receivables, Oracle iStore via Oracle Order Capture, and Oracle Order Management. Most of your effort will go...

Party Model Overview The party model flows through the entire e-Business Suite. There is just one record to represent both a prospect and a customer. The entity itself is recorded, such as a person or an organization. However, customer terms are established, that record represents a prospect. Once customer terms are recorded, that same record now represents the entity as your customer. So, there are no separate lists to maintain and reconcile. In the Oracle e-Business Suite, there is one record to represent Company ABC throughout its full life-cycle. Each application uses different features of the party model. For instance, the Customer Relationship Management Suite (CRM) applications use more details about party relationships and new prospects. The Receivables and Order Management applications use more of the customer accounts including payment terms, billing, and shipping information. The party model contains a unique set of information about a person, organization, or relationship. ...

1. Order Entry This is first stage when Order in enter in system.When the order is entered it basically creates a record in order headers and Order Lines table. oe_order_headers_all (Here the flow_status_code as entered) oe_order_lines_all (flow_status_code as entered) ( order number is generated) 2.Order Booking This is next stage , when Order which is entered in step 1 is booked and Flow status changed from Entered to Booked.At this stage , these table get affected. oe_order_headers_all (flow_status_code as booked ,booked_flag updated) oe_order_lines_all (flow_status_code as awaiting shipping, booked_flag updated) wsh_new_deliveries (status_code OP open) wsh_delivery_details (released_status ‘R’ ready to release) Same time, Demand interface program runs in background And insert into inventory tables mtl_demand 3. Reservation This step is required for doing reservations SCHEDULE ORDER PROGRAM runs in the background and quantities are reserved.Once this program get successfully get com...