Interfaces for Sales Documents with BOS

Use

Using the program interfaces, you can exchange data for the following sales documents with bill of services (BOS):

  • Customer inquiry

  • Customer quotation

  • Sales order

  • Service entry sheet (new process)

  • Service entry sheet (credit/debit memo request)

The following graphic illustrates one possible scenario.

Features

Function modules exist for exchanging data of sales documents.

Several of these function modules have been realized as methods of business object types for sales documents with a BOS. They can be found in the Business Object Repository (BOR) for the industry-specific component Engineering and Construction .

Note Note

You can find detailed information on the business object types and their methods in the BAPI (Business Application Programming Interface) Explorer. You can call the BAPI Explorer by choosing Start of the navigation path Tools Next navigation step BusinessFramework Next navigation step BAPI Explorer End of the navigation path . You can also use transaction BAPI.

You can find detailed information on function modules in the Function Library ( Start of the navigation path Tools Next navigation step ABAP End of the navigation path - Start of the navigation path Workbench Next navigation step Development Next navigation step Function Builder End of the navigation path ).

End of the note.

There following interfaces exist:

  • Create

    Here you can create a sales document with a BOS.

  • Change

    Using Change, you can change specific data in a sales document with a BOS.

  • GetDetail

    Using GetDetail, you can find data for a document. A key identifies the document. Afterwards, this data is returned to the calling program.

  • GetList

    GetList delivers a list of all the documents saved in the system (you can restrict the amount of documents displayed by the search criteria you choose to use) Afterwards, the data on the documents is returned to the calling program. Service data is not transferred.

  • GetDetailedList

    A list of documents is created with GetDetailedList (you can restrict the amount of documents displayed by the search criteria you choose to use) Afterwards, the data on the documents is returned to the calling program. Service data is also transferred.

Customer inquiry with BOS

The following methods replace the function modules used up until now:

Business Object Type

Current Method (BAPI)

Original function module, no longer to be used

CustomerInquiryBos

CustomerInquiryBos.CreateBos

BS01_INQUIRY_CREATE

CustomerInquiryBos.GetDetailBos

BS01_INQUIRY_GETDETAIL
Customer quotation with BOS

The following methods replace the function modules used up until now:

Business Object Type

Current Method (BAPI)

Original function module, no longer to be used

CustomerQuotationBos

CustomerQuotationBos.CreateBos

BS01_QUOTATION_CREATE

CustomerQuotationBos.ChangeBos

BS01_QUOTATION_CHANGE

CustomerQuotationBos.GetDetailBos

BS01_QUOTATION_ GETDETAIL

The following function module is also available as well as the methods above for the customer quotation:

BS01_QUOTATION_GETDETAILEDLIST

Sales order with BOS

The following methods replace the function modules used up until now:

Business Object Type

Current Method (BAPI)

Original function module, no longer to be used

SalesOrderBos

SalesOrderBos.CreateBos

BS01_SALESORDER_CREATE

SalesOrderBos.GetDetailBos

BS01_SALESORDER_ GETDETAIL

SalesOrderBos.GetListBos

BS01_ SALESORDER_ GETLIST
Service entry sheet

The following methods replace the function modules used up until now:

Business Object Type

Current Method (BAPI)

Original function module, no longer to be used

DebitMemoRequestBos

DebitMemoRequestBos.CreateBos

BS01_CDMEMOREQUEST_CREATE

DebitMemoRequestBos.GetDetailBos

BS01_CDMEMOREQUEST_ GETDETAIL
DDIC structures

User data is exchanged in the form of data records. The structures of the data records are archived in the Data Dictionary (DDIC).

DDIC structures (Selection)

Meaning

BAPIVBELN

Sales document number

BAPISDHD1

Header data of the sales document

BAPIRET2

Confirmation

BAPISDITM

Item data of the sales document

BAPISCHDL

Scheduling data

BAPIPARNR

Partner roles for the document header or the SD item

BAPIESLLC

Data of a service line/outline level (excluding long text)

BAPIESLLTX

Long text for service line/outline level

BAPIPAREX

Customer enhancement, import

BAPIBOSCD

Service line conditions

BAPIBOSCOST

Service line cost item

BAPIBOSCOSTMODEL

Service line cost model

BAPIBOSCOSTMODEL_CHARA_VALUE

Service line cost model characteristic
SAP data model

The SAP data records are linked in accordance with the SAP data model.

The following shows the most important assignment rules for data records:

Data record assignment

Implemented with fields

Item data for the sales document - Outline layout

SERVICE_NO - PCK_NO

Outline layout - Service line

SUBPCK_NO - PCK_NO

Hierarchy level - Outline level

HI_LINENO - LINE_NO
Data carrier format

  • The file is organized sequentially.

  • The data records are in ASCII format.

  • The record length of the data carrier is 78 bytes.

  • Every data record in the data carrier ends with the closing character >.

  • Data records longer than 78 characters are split across several data carrier data records. The continuation character is >.

This results in the following data record description:

Symbol

Content

1

Record type or continuation symbol

2-77

User data

78

Closing symbol