CustomerInquiry

The business object Customer inquiry is a customer request to
the company for a quotation or sales information that is not binding.

The request can refer to materials or services, conditions and, if
necessary, delivery deadlines. It is accepted by the sales area that is then responsible for any further processing.


Structure
A customer request comprises several items containing the required
quantity of an item/service. The total quantity can be subdivided
between schedule lines in different partial quantities with relevant
delivery deadlines. Items can be subdivided within a hierarchy which
also makes it possible to differentiate batches and separate bills of materials.

The valid conditions for the items are listed in the item conditions.
They can be distributed from the overall condition valid for the whole request.

Integration

Apart from using the customer as sold-to party, other business partners
can also be specified in different partner functions (e.g. ship-to party).

Available Methods

• Change : Change Customer Inquiry [ BAPI_CUSTOMERINQUIRY_CHANGE ]
  
• CreateFromData : Customer inquiry: Create customer inquiry [ BAPI_INQUIRY_CREATEFROMDATA ]
  
• CreateFromData2 : Customer Inquiry: Create Customer Inquiry [ BAPI_INQUIRY_CREATEFROMDATA2 ]
  

Change

Using this method, you can change or delete customer inquiries.

Header, item, schedule line and configuration data can be changed.

The following is a general rule:

1. Only enter the fields you wish to change.
2. Select the fields you wish to change with an 'X'.


3. Fill in the UPDATEFLAG field with a 'U'.
4. Always enter the key fields when you make a change,even in the checkbox.
5. An exception here is configuration. If you wish to change this, you must fill it in completely.
6. Maintain the quantities and dates via the schedule line data.


7. possible UPDATEFLAGS: U = change
   D = delete
   I = insert

Example

1. Delete inquiry completely.
2. Delete sales document item.
3. Changes to inquiries.


4. Change configuration.

Notes

1. Minimum specifications:

The inquiry number must definitely be entered in the SALESDOCUMENT
structure.
Enter key fields when you make a change.
Always enter the update indicator in the INQUIRY_HEADER_INX.

1. Commit control

The BAPI does not have a database commit. This means that the relevantapplication must leave the database commit, in order that changes canbe carried out on the database. The BAPI BAPI_TRANSACTION_COMMIT is available for this.

CreateFromData

You can use this method to create customer inquiries.

You have to enter at least the header data (using the ORDER_HEADER_INstructure) as well as partner data (using the ORDER_PARTNERS table) as the input parameters.

Enter the item data using table ORDER_ITEMS_IN. You can enter the item
number manually by filling in the relevant field or, if you leave thefield blank, it will be filled in automatically according to the settings in Customizing.

If the items are configurable, you have to enter the configuration datain the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF and ORDER_CFGS_VALUE tables.

Once you have successfully completed the customer inquiry, the systemissues you with the document number (SALESDOCUMENT field) and detailed data about the participating partners (in the SOLD_TO_PARTY,SHIP_TO_PARTY and BILLING_PARTY fields). If there are any errors, the system displays them in the RETURN parameter.

CreateFromData2

Using this method, you can create customer inquiries.

You must enter at least header data (via structure INQUIRY_HEADER_IN)and partner data (via the table INQUIRY_PARTNERS) as input parameters for this.

Enter the item data via the table INQUIRY_ITEMS_IN. Item numbers can be
assigned manually, by filling in the relevant fields, or automatically,according to Customizing, by leaving the relevant fields blank.

If you are dealing with configurable items, you must enter the configuration data in the INQUIRY_CFGS_REF, INQUIRY_CFGS_INST,
INQUIRY_CFGS_PART_OF and INQUIRY_CFGS_VALUE tables.

When you have created the customer inquiry successfully, you willreceive the document number (SALESDOCUMENT field). Any errors that may occur will be announed via the RETURN parameter.

Notes

1. Required entries:
   ORDER_HEADER_IN : DOC_TYPE Sales document type
   SALES_ORG sales organiZation
   DISTR_CHAN Distribution channel
   DIVISION Division
   ORDER_PARTNERS..: PARTN_ROLE Partner role, SP sold-to party
   PARTN_NUMB Customer number
   ORDER_ITEMS_IN..: MATERIAL Material number
   
2. Ship-to party:
   If no ship-to party is entered , use the following: Ship-to party = sold-to party.
3. Commit control:
   The BAPI does not have a database commit. This means that the relevant
   application must leave the commit, in order that changes can be carriedout on the database. The BAPI BAPI_TRANSACTION_COMMIT is available for this.