Objective This note aims to show how to simulate the creation of the Blanket Sales Agreement action using the newly available public API in R12.1.1. . Scope and ApplicationThe target group is for people with technical knowledge of Oracle Applications code, the use of public APIs, and people who are familiar with creating customized solutions for unique business needs. Creating Blanket Sales Agreement using OE_BLANKET_PUB of public APIs. Process_Blanket in Oracle Order ManagementAssumption: The following parameters related to the sales agreement are not within the framework of this document and we assume that these configuration steps are already in place. 1. Setting up the type of booking 2. Set up document sequence 3. Implementation of The “Sales Framework Agreement” function has been created since version 11.5.9 and its creation in order management was supported by the “Sales Framework Agreement” form.
Starting in version 12.1.1, support for the creation of BSA was provided by Backend using the new public API OE_BLANKET_PUB available. Process_Blanket (). Sales Agreement`s feature supports standard items, ATO and kits and also includes the ability to create versions after orders are imported and process control API. The head of the sales contract created usually contains the following information – Debitor, Sending to , Bill to , version e.t.c – Validity dates – Terms of payment and freight between Debitor and supplier – Sale agreementSmin and Max Quantity – Taxation to determine if you can exceed the maximum value – Price information such as standard price lists or price lists for sales contracts. Sales Agreement Lines Include the following information – Categories of items to store categories and ALL ARTICLES to cover all items. – Min and Max amount agreed by customer and supplier – price including the choice of price list in addition to line level modifiers: % discount and discount amount. – Effective DatesProcedure Setting Description: OE_BLANKET_PUB.process-Blanket () accepts the following settings Thanks for your reply. Can you share the procedure with me, please? aloz0101.pixnet.net/blog/post/33472452-oe_blanket_pub.process_blanket setting In/Out Type Description p_api_version_number IN NUMBER API Version x_return_status OUT VARCHAR2 Return Status P_org_id IN Number Org Id (MOAC) P_operating_Unit IN Number Operating Unit (MOAC) p_header_rec IN OE_Blanket_PUB.header-rec-type Head Rec p_header_val_rec IN OE_Blanket_PUB.header-val-rec-type Header Value Rec p_line_tbl IN OE_Blanket_PUB line_tbl_Type Inbound Line Table p_line_val_tbl IN OE_Blanket_PUB.line-val _tbl_Type Inbound Line Values tabelle p_control_rec IN OE_Blanket_PUB.
Control_Rec_Type incoming control record x_header_rec OUT OE_Blanket_PUB.header-rec-type Outbound Header Record x_line_tbl OUT OE_Blanket_PUB line_tbl_Type Outbound Line Table x_msg_count OUT Number Msg Count x_msg_data OUT VARCHAR2 Msg Data p_validate_desc_flex IN VARCHAR2 to FF Validate or not? Does anyone know the API for the sales API and if it can be used for creation and updating? We`re on Exit 12.