SAP invoice

7/24/2019 SAP invoice

1/86

You can create invoicing plans directly for network activities (external, service, or general

costs) or components procured externally.

This means that it is possible to plan costs and outgoing payments on the basis of dates

entered in the invoicing plan. Costs are not simply distributed, but are calculated precisely

at the times specified in the invoicing plan.

You can create an invoicing plan by copying a reference invoicing plan.

The reference invoicing plan fixes cost and payment times relative to a start date.

lternatively, you can copy billing milestones as dates to the invoicing plan of the activity. !f

you copy the milestones rather than creating them manually, they can be postponed

along with the dates in the invoicing plan if the activities are rescheduled.

You cannot create invoicing plans in combination with unit costings (for general costs

activities or material components).

"


2/86

$n the basis of days, periods or fiscal years one can plan payment flows i.e. revenues

and expenditure.

!n %&' elements, manual planning of revenues and expenditure is by period. t

commitment item level (roect Cash *anagement master data) planning takes place.

The +uantity structure in the network and the billing plans in the %&' or ' document

are valuated in the automatic planning of financial data.

utomatic planning will be done by day. lanned line items will be written.

&ased on assignment to -/ accounts commitment items will be determined. 0nlike

revenue and costs calculation, payment date calculation takes account of the

customer and vendor payment terms respectively.

1ote2 The credit side payment plan of the network is determined using theasynchronous network costing only.

The dates and the payment terms are used in the ' billing plan for planning incoming

payments. 'ales order items will also be used in assigning the billing plan data and

payment terms(of the dates or sales order item).The delivery date including the

payment conditions is used if there is no billing plan for the sales order item.

"


3/86"

!n the case of activities processed externally and externally procured components,

invoicing plan including payment conditions are used 4 or, the delivery dates including

payment conditions are used where there is no invoicing plan

!f an invoicing plan has been maintained, payment data is only planned for

general costs activities


4/86

lanned revenues and incoming payments is relevant in billing plan.

ates for own payments are relevant only for payments (not revenues).

*ilestone billing dates appear as planned incoming payments and planned revenues. Two

things are important for dates and amounts i.e. payment terms and payment target

(example2 payment 3 week after invoice issue, with 56 discount)

$nce the proect is executed, invoice billing will be generated and appear in the proect as

actual revenues and customer payment obligations. %ith respect to dawn payment date,

down payment re+uests will be generated by the billing program which are recorded inthe payment data for the proect.

&illing plan can be created for a sales order, a sales order item or for a billing element in the

%&'.

lanned costs and planned outgoing payments are relevant during the !nvoicing plan.

"


5/86"

!nvoicing planes can be created for externally7processed activities, externally7

procured material components, service activities and cost activities.


6/86

epending on the transaction, you can calculate costs for one network (example2 network

maintenance) or a range of networks (example2 all networks for selected %&' elements

in structure planning or the proect planning board).

You can calculate network costs asynchronously. The advantage of this is that you can select

and cost broader ranges (example2 to 8) and carry out costing in the background.

"


7/86

Costing variant controls calculation of planned and actual cost. Costing variant

is assigned to order type. 1etworks are of order category 5#.

The valuation procedure is defined by valuation variant which is a component of

costing variant. &ased on valuation variant prices are determined by the system to

value componenets material, activity type, processes, subcontracting and external

activities. 9aluation variant searches for prices in se+uence from the price sources.

rice entered first is selected first

*aterials2rice is selected either from purchasing date or material master record

ctivity type : rocesses2 rice is selected either from activity based costing or

cost center accounting

;xternallly processed activity2price is selected either from the activity or from

purchasing information record

"


8/86

%hen customi=ing the order value update, you stipulate, for each order category and

type, whether the order or network is appended 7 that is, whether its planned costs are

added to the proect cost plan for assigned %&' elements.

There are two tables for the order type (network type). The first is defined per order type,

the second (parameters for network) per order type and plant.

third important table is the network profile, containing default values for the network and

its activities.

The costing variants for plan and actual costs are determined at network header level.

The costing sheet and overhead key are determined at activity level. They control processcost accounting or application of overhead. epending on the creation process, these

keys are inherited from the network header or the assigned %&' element.

"


9/86

The costing variant contains the basic control information needed to carry out

costing. The valuation variant contains all the information which controls the

valuation of2

*aterial components

!nternal activities

;xternal activities

This information also

controls how

overheads areapplied.

9aluation can be

determined plant by plant.

The ?&y period? indicator enables you to calculate costs for internally7processed

activities period by period.

The costing type contains further detailed information for controlling costing.

"


10/86

You can classify the resources in broadly 5 categories from the networks point of

view2 !nternal and external activities.

!nternally processed activities2 These activities work are carried out by

machines and or persons of own company. You can schedule the activities as

per re+uirement, distribute the work among persons.

;xternally processed activities2 these activities are executed processed by other

companies. These are carried out by purchasing department. The service

activities are also procured externally however different from externally

processed activity that you need to define service specification and the limit for

the unplanned activities which is provided by the service provider.

"


11/86

Business scenario

To execute a proect, materials are re+uired

which can be procured externally (purchasing) or

manufactured in own company (roduction). These

materials are managed in proect7specific stock.

s the proect controller, you are interested in2

The values in the proect, at the different stages of purchasing or production

(proect controlling)

'tocks of raw materials, semi7finished and finished products used for your proect

"


12/86"

(stock controlling)

*aterials provide linkage between many other ' functional modules like

*aterials *anagement (urchasing and !nventory *anagement), 'ales and

istribution, plant maintenance and roduction lanning and Control.

The materials are assigned to activities which helps in material re+uirement and

planning in a proect.

The product which is manufactured in your project is in turn made up ofa variety of material components.

The first step is to plan the procurement and consumption of the requiredcomponents in your project.

Projects are linked to Materials management, Sales and istri!ution and

Production Planning via materials.


13/86

!n order to plan the material re+uirements of a proect, materials can be assigned to

activities. $n the basis of stock, the materials are classified as stock or non7stock items.

The item category stock items (/) are for such materials which are stored in stock e.g. proect

stock, sales order stock or warehouse stock and reservations can be created for such

materials. &ased on the +uantity re+uired in the proect, the re+uirement planning can be

initiated. The procurement element for external procurement is a purchase re+uisition and for

re+uirement planning is planned order.

or productions of assembled material, material &$* is exploded and the

re+uirement planning is executed for all the materials mentioned in &$*.

1on7stock items (1) are for materials which are to be procured directly for the network which

is not using *D (i.e. not procured via proect stock, sales order stock or warehouse stock).

or non7stock items, urchase re+uisitions are created which are passed on directly to

urchasing.

"


14/86

The item category ?stock item? (/) is used for materials kept in stock. %hen you save

your data, the system creates a reservation for the re+uired material. purchase

re+uisition 7 which is passed on to urchasing 7 can also be created for components

procured externally.

The main function of material re+uirements planning is to ensure material availability

(in other words, to procure the re+uired +uantities in time 7 both in7house and for sales

and distribution). This includes monitoring stocks and, above all, creating procurement

proposals for purchasing and production.

!ndependent re+uirements 7 that is, re+uirements for finished products, assemblies or raw

materials 7 trigger re+uirements planning. !n order to cover the re+uirements, order+uantities and dates have to be determined, and the corresponding procurement elements

scheduled. The procurement element for re+uirements planning is a planned order and,

for external procurement, a purchase re+uisition. urthermore, the dependent

re+uirements for materials produced in7house (in other words, the +uantity of components

re+uired to manufacture a finished product or assembly) are determined by exploding the

bill of material. lanned orders are created at each &$* level to cover re+uirements

when a material shortage occurs.


15/86


30/86>


31/86>


32/86

!t is common in engineering proects for critical components with long and unreliable

delivery times to be purchased at an early stage in the proect much before the

proect activities in which the components will be used are specified. dvance

procurement process is used in such situations.

dvance procurement can only be used when you are using sales order or proect

stock .

>


33/86

Order Categories and order types

ocuments are used to enter business transactions in the D" 'ystem. $rders are

one type of business transaction. $rders are determined by their order category.

The network is an order category. $rder types are prescribed by the system for the

relevant applications.

You can define your own order types within an order category. The order type

describes how the order is controlled.

Customi=ing includes two tables, one for the order type and another for the

order typeplant combination.

The order category is used to control2

3. 1umber assignment

5. efault value settings

". 0ser7specific status management


34/86>

You can assign various ' orders to a proectF examples include internal orders,

production orders, and plant maintenance orders. You can then use the proect

hierarchy reports to evaluate these assigned orders with the %&' element.

;ach order is a cost obect with its own costing parameters such as planned costingvariant, actual costing variant, and overhead sheet. The planned costs of assigned

orders are used to determine the planned costs of the proect.

You assign orders to the proect either by assigning a %&' element to the order

header or by assigning the order to a network and activity as a subnetwork. !f the

assignment is re+uired only for cost control and analysis, you need to assign order to

the relevant %&' element. !f the assignment is re+uired both for scheduling and

cost control, you need to assign the order as a subnetwork. The %&' element is

derived from the network activity. 1ote that production orders cannot be assigned as

subnetworks.

ocuments are used to enter business transactions in the D"

'ystem. $rders are one type of business transaction.

$rders are determined by their order category.

The network is an order category. $rder types are prescribed by the system for the

relevant applications.

You can define your own order types within an order category. The order type

describes how the order is controlled.

Customi=ing includes two tables, one for the order type and another for the

order typeplant combination.

The order type is used to control2

1umber assignment

efault value settings

0ser7specific status management 0ser7

specific field control

lant and order type parameters are used to control2

!f the network is activity7 or header7assigned

lanned and actual costing variants

The settlement rule strategy


35/86

You can use the ?appended? indicator to specify, per order category, whether an

order is appended 7 that is, whether the planned values for the order are included

in the planned value of the corresponding %&' element2

3. !f the ?appended? indicator is set, the order planned value increases the

%&' element planned value. The information system shows the total

as the proect plan. %hen cost planning is taken over as the budget,

the values from appended orders also contribute to the budget.

5. !f the ?appended? indicator is not set, the order planned value is not

added to the %&' planned value. !n budgeting, the plan total for such

orders must be added manually so that these orders can use funds

later.

>


36/86

You can use the ?appended? indicator to specify, per order category, whether an

order is appended 7 that is, whether the planned values for the order are included

in the planned value of the corresponding %&' element2

$nce released, all orders are apportioned 7 this means that their plan, commitment,

and actual values are funds assignments against the funds in the proect. The

order value table contains an indicator which you can use to make orders

?apportioned? earlier, at the ?created? stage.

You can set appended and apportioned indicator based on the order category,order

type, and controlling area

n exception to apportionment at release is in the case of networks for preliminary

planning.!n roect 'ystem customi=ing,you can specify network types to be used

for preliminary planning.reliminary planning networks are never apportioned.Their

related plan values do no increase the assigned value for the relevant %&'element

!n the case of networks (order category 5#), you can use the network type

parameters to determine whether the network is2

Geader7assigned or activity7assigned 7 that is, whether costs are managed in

the network activities or collected in the header

>


37/86>

preliminary planning network whose plan, commitment, and actual values

are not apportioned 7 meaning that they do not appear as assigned values

in the proect.


38/86

Header-Assigned Networks

!n a Geader7assigned networks all the costs (activity and material) are assigned at

network header level

fter assignment of network header to a %&' element, ll costs are transferred to

%&' element. ssignment of activities to %&' elements is only to summari=e thedates

%e you have to use header7assigned networks to assign networks to sales order in

case sales order are not assigned to proects as no assignments can be made to a

sales order item in the network activity.

Activity-Assigned Networks

Costs are collected on activities in case activites are used as account assigned

obects.lantnetwork type parameters deines the condition if the network header

or network activities are to be used as cost obects.

ctivity7 assigned networks are usually used when activities are assigned to various

%&' elements.Gere every activity in the network is an account assignment obect.

%hich implies we can analy=e planned costs, commitments and actual costs

for each activity.

The costs are aggregated and displayed for the %&' elements to which

the activities are assigned.

>


39/86>

ctivity account assignment is a special feature of networks. ll other order types are

header7assigned. ctivity account assignment is controlled via the appropriate

indicator in the table ?arameters for network type?.

Geader assigned networks should be used when networks are assigned to salesorders without %&'.Geader assigned networks can also be used when the

enitre network is assigned to a single %&' element


40/86

' document item assignment is controlled via the account assignment category.

The account assignment category is controlled via ' re+uirements type

determination.

!mportant factors that affect account assignment are the strategy group, the *D

type and item category group from the material master of the product as well as

the document type of the ' document.

The system defaults the item category when you create an order. You can accept

the default or overwrite it. ermitted item categories are defined in Customi=ing.

The permitted planning strategies are assigned to the material using the planning

strategy group. This is necessary so that you can find the correct re+uirements type

in independent re+uirements management and sales order management.

The default re+uirements type is the main strategy in the planning strategy group.

!f no planning strategy group is defined in the material master, the system uses the

item category group (sales and distribution screen in the material master) and, if

necessary, the *D characteristic to search for the re+uirements type for the salesorder.

>


41/86

The account assignment category determines the C$ obect to which document

+uantities and values are assigned. You use it to determine the following2

0sing the special stock indicator (''! above), that goods movements in /ogistics use

plant stock, sales order stock or proect stock.

0sing the consumption posting indicator (Cons. above), the C$ obect to which the

values of a material document are assigned.

'ettings2

H Collective stock, consumption posting to the consumer (order, activity)

The account assignment category is important for procuring components directly.

; H Iuantities and values managed in the sales order item

This account assignment category is important for make7to7order production without

%&'.

H Iuantities managed using sales order item, values managed in proects

This account assignment category is important for non7valuated proect

stock, with %&' and sales order item

I H Iuantities and values managed in proects

This account assignment category is important for proect stock

>


42/86>

- H lant stock, values managed using proect

This account assignment category is important for sales order items sold

from plant stock, with

value posting to the proect. !t differs from account assignment category ?? in

the field control

of the account assignment block.


43/86

ctivity7&ased Costing offers a facility for allocating and distributing the overhead to its cause.

ctivity7&ased Costing provides useful information on2

$verheads reduction by process improvement

rofitability increase by highlighting unprofitable products or customers

ctivity7&ased Costing is advantageous for having2

J Transparent overheadsJ arallel +uantity and value flows

J recise assignment of internal activities to consumer

Keanut butter effect? can be avoided through even distribution of overheads among all

the cost drivers.

@


44/86@

!n ctivity7&ased Costing, processes are the controlling obects. rices can be either

maintained manually or using activity and cost input planning in the case of cost

centers and activity types. Through activity based costing, processes are debited to

cost obects or profitability segments.


45/86

Templates are created in LCustomi=ingM and determined by controlling area, costing sheet,overhead key and template environment (for networks 4 ##


46/86@

proect

Calculated value to be added to the

proect at the start, end or continuously

The price for the process and the allocation cost element are determined by

entering one process per line in the process template. *ulti7level processes can be

mapped by referencing another process template in the working template.

The +uantity used by the cost obect is determined using the cost driver. This enables

the allocation of the relevant values to all the levels in the process hierarchy as far

as cost obects or profitability segments.

Cost drivers can originate from many different sources in the D" 'ystem or external

systems. ;xamples 2 weight (material master), number of components, activities of a

particular category, work center (network), number of sales orders for market

segment (/!') etc. The +uantities determined by the cost driver are multiplied by the

price of the process. The resulting value is charged to the cost obect (in the

example, the %&' or networkactivity), and the process is credited.


47/86

ctual prices for activity types and business processes are calculated in $verhead

cost controlling at the end of the period.

ctual prices H ctual costs Iuantities consumed

The possibility of revaluation at actual prices and its specification for each

activity type are controlled in Customi=ing in the parameters for the actual

version depending on the fiscal year.

The difference between the actual price and the originally allocated price is

charged to the cost obects.

Devaluation at actual prices for activities and business processes can be done

in the roect 'ystem and in the Cost $bect Controlling.

Devaluation at actual prices using an activity type is illustrated in the example given

in the slide

@


48/86

$verheads calculation is used to allocate overhead costs to cost obects such as activities

and %&' elements. Calculations are done based on the Costing sheet entered in

the cost obect and the overhead key entered on the %&' element,network header or network activity. $verheads can be calculated for

planned, commitment and actual values. $verhead calculations are

done using the +uantity based or percentage allocation rates.

The following postings get generated through overheads allocation2

ebits to cost obect (%&' element, 1etwork header or1etwork activity )

Credits to cost center ( overhead order or process )

@


49/86@

$verhead costs are updated using the secondary cost elements

in the costing sheet credit rows and these can be simulated also.


50/86

Costing sheet is derived by means of the costing variant from the ?arameters for

1etwork Type? table, in the case of networks. The costing sheet and the overhead key

can be changed in the network header.

The costing sheets to be used in the activities are made a default through this.

or %&' elements, the costing sheet is derived directly from the proect profile. !n

the case of ;asy Cost lanning and the unit costing for %&' elements, the cost

planning draws on a costing sheet for a costing variant which is assigned to the

proect profile through the planning profile.

$verhead keys for activities are inherited from their respective %&' elements.

@


51/86

$verheads are calculated using a costing sheet.

The overhead surcharge can either be a percentage if it is value driven or an absolute value

of measure if it is +uantity driven. The overhead is calculated against a base which is defined

by the cost elements. Cost elements or cost element areas are collected in base lines.

actors such as Controlling area, company code, plant, overhead group, network type, time

period and plan versus actual determine the overhead rate applied. $verhead key assigned

to the cost obect decides the determination of overhead group in customi=ing. Thus a single

costing sheet with flexible rates can be made use of different organi=ational units or

individual activities.

@


52/86@

networksactivities.

s part of the network costing, the system automatically determines planned

costs when you plan dates and resources for the following obects2

a. or internally processed activities2 activity inputs

b. or externally processed activities : service activities2 rimary costs

c. or genreal costs activities2 primary costs

d. *aterial componenets2 primeary costs.

You can use planning templates to create +uantity structures for ;asy Cost

lanning.

You can enter +uantities and prices in the template, or regulate activation using

formulas or conditions.

You can use characteristics assigned to the planning template as variables for the

formulasconditions. The characteristics are valued by the user when theplanning templates are copied into ;asy Cost lanning.


53/86

0nit costing is done to calculate cost plan per %&' element. Gere we use

planned +uantities instead of cost.

!t is not period dependent

t cost element level, plan values are displayed

!nput information related to sources of supply, +uantities and prices mark the useof unit costing to generate cost plan per %&' element

@


54/86

Structure Oriented Panning!

'implest type of planning is structure based planning. lan values are displayed

in hierarchy

The total cost planned is aggregate

!t is neither by cost element nor is period specific

9arious views are used to display the different values in structure7oriented

planning

lanned total 9iew7this shows total aggregate at superior %&' element (/evel

3 %&' element)

The distributable or distributed view7This view is used to check distribution of

budget among child %&' element

Cumulative or remainder view7This view is used to check distribution of budget

across years

$rdernetwork view7This displays the planned cost od appended ordersnetworksassigned to %&' element

Cost Element Planning/Activity Input Planning:

%hen more detailed information is re+uired, cost element planning is done. !t

is independent of proect scheduling

*anual reschedule of cost planning becomes mandatory if a proect or

individual

@


55/86@

package schedule is changed

This planning is adopted if precise information is available as it becomes sure not

to reschedulepostpone the proect


56/86

The plan profile is used to control overall costrevenue planning. !t contains costing variants

for the unit costing or ;asy Cost lanning.

!t also contains indicators for updating revenue plan values via customer +uotations or sales

orders.

You assign the plan profile to the proect by way of the proect profile. You can change it in the

proect definition.

Costs and revenues can be planned in different C$ plan versions.

You either specify the plan version during planning or, if you are using ;asy Cost lanning,

you assign it to the controlling area.

lanning layouts are used to plan costs, revenues, payments, and statistical key figures.

You can use the Deport ainter to create the layouts and can assign them to planner profiles.

0sers can choose planner profiles and assign them to the user master record.

lanning profile2 0se transaction $'&

The lanning profile contains the settings related to planning. !t control overall

costrevenue planning. lanning profile is assigned to proect using proect profile. Costing

variant are

@


57/86@

relevant if we are using unit costing and easy cost planning

C$ plan version is re+uired to be specified if we are using easy cost planning.

lanner profile and planning layouts are specific to use of detailing planning

using Kcost elementactivity inputN


58/86

lanning profile is contains the settings for overall planning, detailed planning

and unit costing

etails for each field can be checked using

3 !mportant field details are as2

Total 9alue2 efines overall planning without any reference to fiscal year

nnual lanning2 efines overall planning with reference to fiscal year

&ottom up lanning2 $verall planning values are extrapolated after saving

;xchange rate type2 etermines which exchange rate is to be used for currency

conversion of overall values

A


59/86

Transaction $OOT to edit costing and valuation variant

Costing variant is mostly used for unit costing ,easy cost planning and also used for

costing networks. The field costing type determines for which %&' element

(costing obect) costing is done

9aluation variant determines the prices and rates. !n the above mentioned slide,system will first check for Klanned price 3N if it fails, system will check for Kstandard

priceN and again if it fails it will check for Kmoving average priceN from material

master. !f system now fails, it will trigger an error message during cost determination

A


60/86

"nternay-processed activities!

!f no distribution key or work center is maintained in the activity, the costs are distributed

evenly over the earliest dates in the activity. 9aluation is at the rate in the valuation variant.

epending on the strategy being used, the system can determine the most current date.

valuation is determined by the rate maintained in the valuation variant. &ased on the

strategy adopted, system determines the latest date. !f no work centerdistribution key is

maintained, the system distributes the cost evenly over the earliest dates.

Costs activity!

Case 32!nvoice plan maintained2the values in periods are as per the values mentioned

in invoicing plan

Case 52!nvoicing plan not maintained and distribution key maintained2The activity value

is

A


61/86A

distributed to the periods based on the distribution key maintained in the activity

Case "2!nvoicing plan not maintained and distribution key not maintained2The

costs are distributed evenly over the earliest dates in the activity

!f an invoicing plan has been maintained, the values in the periods are set

as specified in the invoicing plan.

$therwise, the activity value is distributed to the periods using the distribution key in

the activity. !f no distribution key is maintained in the activity, the costs are distributed

evenly over the earliest dates in the activity.

Service activities or e#ternay-processed activities!

Case 32!nvoice plan maintained2the values in periods are as per the

values mentioned in invoicing plan

Case 52!nvoicing plan not maintained2The activity value is set in the period of the

latest activity start date.lso the system determines the price from the purchasing info

record or the activity value.

!nvoicing plan has priority for the values

!f an invoicing plan has been maintained, the values in the periods are set

as specified in the invoicing plan.

$therwise, the activity value is set in the period of the latest activity start

date.

The invoicing plan has priority for the values. !f no invoicing plan has been

maintained, the system determines the price from the purchasing info record or

the activity value.

$ateria components!

Case 32!nvoice plan maintained2the periods and ,in some cases,values are

taken from invoicing plan

Case 52!nvoicing plan not maintained2The system determines the price from the

purchasing info record or the price is taken from material master as per

valuation variant.Gere material re+uirement date determines the period

!f an invoicing plan has been maintained, the periods and, in some cases, the

values are taken from the invoicing plan. !f no invoicing plan has been maintained,

the values are taken from the purchasing info record or the price is taken from the


62/86A

material master per the valuation variant. !n this case, the period is that from

the material re+uirements date.


63/86

The customer accepts the +uotation. sales order is created in the system, where

appropriate using the +uotation as a template. The activities listed in the +uotation

are entered in the sales order as sales order items.

The items are assigned to the proect. They are used for revenue planning and for

posting revenues to the proect by means of milestone billing.

Two companies are responsible for executing the proect 7 !;' - and !;' 0O.

!;' 0O creates a sales order for !;' - and assigns the document item to the

billing element T73##PP.3.5.

/ater on, !;' 0O bills its services to !;' - on a resource7related basis.

billing re+uest is created in the system via resource7related billing. This is billed and

results in revenues for !;' 0O.

A


64/86

!n ' where proect is a controlling obect2

'ales order created and after structuring of proect sales order will account assigned to%&'. Then revenue planned in sales order.

$nce %ork completed in proect, actual cost captured in %&' and inal product will

be delivered to Client.

&illing will be completed and actual revenue generated. ctual Devenue will

be transferred to %&'.

%hile Desult analysis performed for proect the ctual Devenue and Cost will settled

to the profitability segment.

Sae document structureJ 'ales ocument type represents the type of business transaction and functions and

the flow of document with in sale order. rocessing.

J !tem Categories are assigned to sales document category. %hile creation of 'ales order

it will default the item category but user can change it as per re+uirement.

J 'chedule line category is assigned to !tem Category. %hile creation of document

system will default the scheduled line category but it can changed according to

re+uirement.

A


65/86A

"tem Category

J Item Category is determine by Sales Document type and thematerials Items category group in a sales order.

J Item Category controls function for Sales Order like Item Type,Pricing, illing Plan, resource related or deli!ery related.

J It controls if pricing is rele!ance for billing, rele!ance for Deli!erySchedule "ine Item, and contains Incompletion "og and Partner te#t.


66/86

(3)Depresents a process of make7to7order production without a work breakdown structure.

!n this case, the sales order item is the contolling instrument. ccount assignment category

; specifies that the sales order item forms a separate C$ obect.

Costs and revenues of the sales order item are usually settled to the profitability segment.

(5)0sing assembly processing, you can generate a network when you create the sales order.

%hen you save your data, the system creates a %&' and assigns the sales order item to a

%&' element in this %&'. !n this case, the sales order depicts the sales view, the proect is

the controlling instrument, and logistical processing is represented by the network.

ccount assignment categories or I (Cons. H in each case) specify that revenues

are assigned to the billing %&' element of the proect.(")s an alternative to assembly processing, you can assign a sales order item to a %&'

element in a proect. Controlling takes place in the proect. You can assign orders or

documents to the proect. 9alue assignment to the proect is controlled via account

assignment categories -, and I. These differ from each other in the way that they

manage +uantities.

A


67/86

*ethods for plan revenue in a proect are2

a. *anual revenue planning2 this can be based on structure or revenue element

where the later is a cost element and period based.

b. ' billing plan2 this is cost element and period based planning.

c. ' document2 this is part of integration with ' module where sales order itemor +uotation items are used as revenue planning. This kind of planning is cost

element and period based.

A


68/86

Devenues can be planned in proects using the following methods2

*anual planning in billing elements in the proect structure.

This type of planning can follow the same procedure as cost planning, or can be by

revenue element.

'ales orders (all ' documents assigned).

'ales order items are assigned to %&' elements. !n Customi=ing, you can stipulate, for a

combination of sales document category (+uotation, order, and so on), sales

document type, controlling area, and system status, whether the billing data (for

example, in a billing plan) from a sales order should update the revenue plan for an

assigned %&' element. The dates and planned revenues concerned originate eitherfrom the billing plan for the sales order items or (if there is no billing plan) from the

net value and apportionment data for the item. The revenue element originates from

-/ account determination in '.

&illing plan in proect billing elements.

The revenue element is defined in Customi=ing.

A


69/86

There are different ways of creating billing plans2

*anually

&y copying a reference billing plan

!n ' and ', reference billing plans can be

called upon automatically

&y copying billing milestones from work

breakdown structures or networks

&y copying billing milestones automatically from

the network in assembly processing

A


70/86

!n the ' document, you can define a detailed billing plan with a number of billing dates

instead of ust a single billing date. billing plan is a schedule containing individual billing

data for a particular sales document.

*ilestone billing is widely used in proects (for example, construction proects).

!f you use milestone billing, the total value to be billed is apportioned to the individual dates

in the billing plan per defined rules.

&illing plan dates can be blocked for billing

You can set billing blocks manually or remove them by activating billing milestones.

s of Delease


71/86B


72/86

The term ?Version" is used in the proect system in different contexts. ifferent

types of versions include simulation versions, proect versions and C$ planning

versions are available in ' roect 'ystem which are discussed below.

roect versions, are snapshots of a proect at a specific point in time, and are

used for documenting the progress of a proect over time. &oth +uantities and

values are stored in versions and it can be created either manually, or

automatically when a status changes. !n the case of status change, the proect

profile contains a reference to a version profile which specifies the name of

the proect version to be created when a particular user or system status is

set.

'imulation versions2 !n the roect 'ystem, these are versions that you can

change. You might, for example, create simulation versions in the following

situations2

!n the +uotation phase2 generally speaking, at this stage there is not yet

an operative proect.

To draw up alternative planning scenarios for existing operative proects

or parts of these.

C$ plan versions are used to plan revenues and costs. You can copy values

from one version to another. You can change planned values manually in every

version and cost values are retained.

B


73/86

'imulation versions are used to draw up alternative ?what ifQ? planning

scenarios. They are created manually, can be changed, and, if necessary,

deleted again which is unlike released operative %&'s with activities.

'imulation versions are useful during the +uotation phase of a proect

and possible to plan several simulation versions.

You can create simulation versions even at the time of execution of proect,

where you can copy from operative to simulation versions, compare, analy=e

and work with other versions and transfer them back to the operative

proect.

%hen an operative proect is copied to a simulation version or vice versa, a

log file is created which contains the obects that were transferred and any

error messages that were issued in the process.

'imulation versions can be created either for an entire %&', or for

sub7 hierarchies of a %&'.

'imulation versions are edited in the proect planning board or in proectplanning board from ' D"


74/86

'imulation customi=ation consists of two steps2

3. 9ersion keys2 one should work with permissible version keys since these cannot

be deleted once simulations has been created.

5. 'imulation profile2 This determines which all obects will be copied while creating

simulations (in addition to the structure information) from simulation tooperative (and vice versa). !f there are no simulation profile, all the texts will be

copied. The simulation profile will be defaulted in the proect due to assignment

in proect profile.

Rust like proect version, simulation versions can be compared with each other in

information system, whereas the cost element report does not support the

simulation versions. 0nlike operative proects, simulation versions cannot be

changed in structure info system.

B


75/86

%hen you transfer data from operative proects to simulation versions (or

vice versa), the following obects are copied2

%ork breakdown structure

1etwork with activities, activity elements, relationships, and

subnetworks *ilestones

*aterials for the activity

ocuments, ' texts and long texts (depending on the simulation profile

used)

Capacity re+uirements

!nvoicing plan for the network, and billing plan for the %&' element

(as of Delease )

The following obects are not copied2

$ther orders (e.g. no production orders)

roduction resourcestools

B


76/86

roect versions enable you to record a snapshot of a proect at a specific

moment in time 7 this can be used for future comparison with the

operative proect.

You can create a proect version automatically (i.e. triggered by a system or user

status).

You can also create a proect version manually2

%hile changing the %&'

%hile changing the network

!n the 'tructureates information system for one or more proects

ata transfer when 9ersion profile settings are used while using these transactions2

3. 'tatus dependent proect versions.

5. TC network maintenance C155 or %&' element maintenance CR#5

ata transfer which is !ndependent of version profile and dependent on

database profile2

". TC C1A3 and C1A5


77/86B

The version profile is maintained in the ' customi=ation and assigned to

roect profile or network profile.


78/86

You use a version profile to define two different kinds of information. irst, you

specify which version is created automatically when a specific system status or

user status is set. 'econd, you specify which data is to be written to the

versions that are created automatically.

You need to define a version profile, if you wish to have versions created

automatically, or if you wish to generate versions directly when editing the %&'

or networks.

You do not need to define a version profile, if you wish to generate versions

manually from the 'tructureates information system.

The version profile is entered in the proect profile and network profile.

B


79/86

roect planning board is a tool in ' ' which helps and enable you to

process edit the entire proect structure which are %&' element, activities,

relationships, milestones, material components, ' texts, documents and

assigned obects to them.

!t is similar to -antt chart based on interactive ' environment.

This comprises of hierarchy structure of your proect and the corresponding

date situation.

You can custom made the display in proect planning board to suite your

re+uirement.

roect planning board can also be useful for planning dates and resources

i.e. work, external processing, for planning costs using activities.

B


80/86

roect planning board profile contains default values for the appearance

of planning board.

The settings in this proect planning board profile is valid for both, simulation

versions and operative proects.

The graphical display can be changed and adapt as per user needs inthe planning board and customi=ation using proect planning board

assistant.

B


81/86

roect planning board is a graphical interface based on -antt chart which can

be used for creating and maintaining data like proect definition, %&' element,

activities, relationships, milestones, documents and ' texts.

0seful for 'cheduling and monitoring.

You can view date view, and other overviews of proect at the bottom of -anttchart like capacity overview.

You can view logs, hierarchal graphic of %&' element and 1etworks and

network activities.

This is the only transaction where we can change simulation versions for

releases earlier than ' D"


82/86

ssembly processing will be helpful while one is planning and producing or

servicing same product for several times with similar constellations. %hich means

the basic structure will be same while data like duration, dates, +uantities etc. will be

changing. !n assembling processing, a network and %&' element : roect (if

re+uired) is automatically created based on the customi=ation, while a sales

document is created and saved. The proect number is derived from 'alesdocument and this process generates assignment between sales document :

proect. This incurs that the same information will be shared by sales and proect

team. !f the data is changed in roect will update 'ales document (and vice versa)

which helps in delays and disagreement between sales and proect department.

rocess flow2

!f a sales order is created for a material which has strategy group for assembly

processing has been assigned, the assembly processing will start.

The *D processing is omitted in the assembly processing and creates a operativeorder (network in case of ') directly from sales order.

ssembly processing is carried out statically in ' which means only one network

for one sales document item.

&ased on the customer re+uirements date, backward scheduling is carried out and

availability check is done for re+uired material components. %hich enables to

inform customer about feasibility of re+uired date or else system will propose new

date.

E


83/86E

lso, the calculated cost will be transferred from network the sales order.

%hile saving the sales document, %&' element structure : proect definition will

be created which is identified by sales order number.

'ince the sales document and the proect is directly connected, any changes

one obect will update reflect in other automatically.


84/86

The re+uirement class which is assigned with the sales order while creating it will

start assembly processing, one assembly order automatically created by system

and start assembly processing in the back ground. &y this method *D is ignored

and an operational order created directly from 'ales $rder.

&elow is the list of ssembly order which can be created27

1etwork, roduction $rder, planned order, lant maintenance or 'ervice order and

rocess $rder.

ssembly rocessing contains all the date of 'ales order and assembly order. 'o

if there is any change done later to any document it will reflects in both document.

E


85/86E


86/86

Documents

SAP invoice