Actividad aeronáutica

It is a condition type for copying cost from line items. This is the condition type that we want to use to determine the results of the sales order pricing for SD document item.

If we enter this condition type in requirements class then it applies to all sales document items that containing requirement type which indicates requirement class. If we enter the condition type into the sales document type this condition type is used for all items in the sales documents of this sales document type. EK01 and EK02 have been provided for cost transfer of line items.

 EK01: If we choose it the result of the sales order costing (integration with controlling) is first printed to the pricing screen for the item. The value can be used as a basis for price calculation.

 EK02: System simply takes the result of the sales order costing as a statistical value (only for information purpose).

Billing plan type: [] We can assign billing plan type for this sales document type as an Ex: Standard billing,

periodic billing (for rented or maintenance contract). The entire value to be billed is billed in each billing plane date.

 Milestone billing (for) projects: The total value to be billed is distributed between the individual billing planned dates (that can be amount or percentage wise).

Payment guarantee procedure: [01] = Standard

The key identifies the document payment guarantee procedure for this sales document type. It defines which payment guarantee procedure system automatically uses for this sales document type. With in receivable risk management system determines payment guarantee procedure by taking following factors into consideration.

(A) Key of document payment guarantee procedure from the header of the sales document type. (B) Key of customer payment guarantees procedure from customer master.

The payment guarantee procedure defines the type and sequence forms of payment guarantee that the system assigns to sales document types.

Payment card plan type: [03] = Payment card

It specifies the payment plan type for payment cards. The payment card plan type specifies how the sales document to which it is assigned will be settled for payment in this case one or more payment cards.

Checking group: [01] = Standard

It specifies how the system carries out checks on payment card data in different SD documents. It is done on the basis of checking group assignment to different sales document types.

Requested delivery date/Pricing date/Purchase order date Section

This section deals with default dates for delivery pricing and purchase order date.

Lead-time in days: [7]

It specifies the number of days after the current date that the proposal for requested delivery date in the sales document should be.

Date type: [] It identifies the date type internally in the system. When we create schedule lines for the sales

document types we can specify different formats for the delivery date.

Proposal for pricing date: [] = Proposal based on today’s date.

Proposal for pricing date is based on the requested delivery date. We can enter the date, which we want the system to propose for the pricing date when sales document is created.

Ex: We want the date on which the contract becomes valid to be the date, which is proposed, has the pricing date in

the sales document. So that value “B” can be set here.

Proposed valid from date: [] No proposal

Specify the ID for the date which, the system proposes for valid from date.

80

Propose delivery date: It indicates whether the system automatically proposes the current date as the delivery date. Propose PO date: System proposes current date as a purchase order date.

Contract section

This section deals with contracts documents.

Pricing procedure condition Header: [] Pricing procedure for conditions at header level Ex: PABR01. We can

assign a procedure for contract document header level that applies to all items in the contract document. This procedure can be assigned for service items.

Pricing procedure condition Item: [] Pricing procedure for contract conditions at item level Ex: PABR02. We

can assign a pricing procedure for contract documents at item level. This procedure applies to only item.

Contract profile: [] For contract documents we can define contract profile in which we can specify contract

validity periods and cancellation rules that system automatically uses.

Billing request: [L2] = Debit memo request

We can assign billing request L2 (debit memo request) for business compensations.

Group reference procedure: [SDGK]: We can assign a reference in procedure to which master contracts and

lower level contracts can be linked with each other.

Contract data allowed: [] = No contract data allowed for order type.

The value of this field determines:

(A) Whether the contract data allowed for this sales document type that we enter. (B) How the changes affect that we made to header level.

 Values: “X” or “Y”

 If it is “X”: If we set “X” the change that we made to the header level will not be copied to the items, it applies even the header data is identical with item level data.

 If it is “Y”: If we set “Y” the changes that we made to header level copied automatically into items.

Follow up activity type: [] Ex: 0003 = Sales letter

We can specify the follow up activity type that is to be created when sales activity is defined as the follow up action for this kind of contract sales document type.

Ex: Follow up activity type 0003 can be assigned with contract document type “MV” (rental contract). We can

create follow up activity work list by choosing outline agreements  contract  subsequent functions  follow up actions, then enter selection criteria, select all contracts with follow up action that is created sales activity and choose edit follow up actions. Then system automatically proposes follow up activity type 0003.

Subsequent order type: [] It’s a proposal for order type for the subsequent functions. We can assign an order type

that system proposes automatically with in subsequent processing.

Ex: For maintenance contract (that has a validity period one year) we can create follow up action that is create

quotation that is to be carried out before the contract end date. We can assign order type “AG” as a follow up action.

81