New Fields

8/10/2019 New Fields

1/63

How To Create Field in KOMP, KOMG

New Fields in Pricing

To use a field in pricing, one creates a condition table. This condition table is created

using the allowed fields from the field catalog. Should the fields one requires not beincluded in the list of allowed fields, one can add the fields from the list of available

fields. However, one may find that a new field may not be in the list of available fields.

For this reason, one must create new fields for pricing. The document and item data in

SD is stored in data tables, such as V!" and V!# $for the order transaction%. &any ofthe fields from these tables are available in the field catalog.

The field catalog is a structure $"'&(% that consists of two tables $"'&" and "'%.These tables contain the header and item data for pricing respectively. They are called

"'& )*+ because they are communications structures used to communicate the

transaction data with the pricing procedure. Table "'&( contains the fields of tables

"'&" and "'.

f you require a field that is not in "'&(, it means that it is not in "'&" or "'.This means that the field you require cannot be used in pricing because there is no

communication of this field from the transaction to the pricing procedure via the

communication structures.

To use a field not defined in the field catalog, you need to add this field to the "'&" or

"' structures, and then write the !!# code to transfer the data in the field from the

transaction tables to the communication structure. Follow these steps-

. /reate the field in the "'&" $header data% and "' $item data% tables using thestandard includes provided for this requirement.

0. 1rite the code in the user e*it to read the transaction data and transfer it to the "'&

)*+ structures.

&enu #ath

The menu path here is &(, Sales and distribution, System modification, /reate new

fields $using the condition technique%, 2ew fields for pricing.

Adding the Field to KOMK and KOMP

This process requires some 3nowledge of the !!# dictionary and how to use the !!#

dictionary to create and change fields and tables. 4ou may have to use an !!# s3ill toassist you. f the field is from the header table $for e*ample, the order table V!"%,

you5ll need to add it to the include table "'&"!6 in table "'&". f the field is from

the item table $for e*ample, the order item table V!#%, you5ll need to add it to theinclude table "'!6 in table "'.


2/63

7et5s say you need to use the )base material+ to define a price and the base material is not

in the pricing field catalog. The base material is a field on the material master basic data

screen and is defined as &!8!918"ST. Since this relates to the material, it is at theitem level, so you would add the field to the "'!6 include table.

2ote 1hen you add a field to these tables, it must start with )66.+ Therefore, the

field you add would be 6618"ST. n !!#, when you add the field, use the samedomain as in the field in the original table &!8!18"ST.

!fter adding the field, generate the structure "'. This field is not available in the fieldcatalog and can be used in condition tables.

Writing the ABAP Code

The field in the communications structure will be blan3 unless the !!# code transfers

the data from the material master to the field "'"ST. #ricing occurs in the

order and in the invoice, so you need to put this code in both places. For the order

transaction, write the !!# code in user e*it:S;8;


3/63

!ssuming that one of the 3ey combination is !ccount !ssignment (roup, you will have

to chec3 whether have the !ccount !ssignment (roup been input in the /ustomer &aster

$illing tabstrips 9 !ccounting sections 9 Field name- !cct assgmt group%.

The !ccount !ssignment (roup will be copied automatically into the sales order.

/hec3 whether the configuration in transaction V"'! have been done correctly.

/hec3 whether the sales order $V!AE 9 (oto 9 Header 9 Financial !ccounting 9 Field

name- !cct!ssg(r% have been filled in automatically.

/hec3 whether the billing document $VFAE 9 (oto 9 Header 9 Header 9 Field name-!cct!ssg(r% have been filled in automatically.

f the customer master have not been maintained and the user have already input the sales

order, then the user will have to maintained the !ccount !ssignment (roup manually

either in the sales order or the billing documents.

Ta3e note for 'ne Time /ustomer, the user have to input the !ccount !ssignment (roupmanually into the sales order. 'ne Time /ustomer can be used by many customer,

therefore, the system will not be able to determine the !ccount !ssignment (roup

manually.

!e"alt #tart $ariant "or $F%&

There are two types of variant in $F%&.

'ne is the selection variant before clic3ing the !is'la( Billing )istutton.

4ou can set the start variant via #*+using the Changemode.

The second variant is the Billing )a(otdisplay variant.

This is after clic3ing the Display illing 7ist utton.

!fter creating your layout display variant, you can set it by clic3ing -9

#ettings9!is'la( $ariant

9 Ad-inistration

Select the layout display variant you want and clic3 -9


4/63

*dit9

!e"ine de"alt settings

Condition *.clsion which will be

deter-ined in the billing doc-ent

The s(ste- can e.clde conditions so that the( are not ta/en into accont dring

'ricing0

For e.a-'le1

Material &233 costs 34% 5#!0 #o-e csto-ers recei6e a discont o" 3% 5#! 'er 3%%

'ieces0

Howe6er, a s'eci"ic csto-er can b( the -aterial "or 3%% 5#!0 #ince this is a

'articlarl( good 'rice, the csto-er shold not also ha6e a discont o" 3% 5#! 'er3%% 'ieces0 There"ore, this discont is to be e.clded "ro- 'ricing0

To create a condition e*clusion procedure which will be determined in the billingdocument.

!ssign the procedure to the pricing schema, and maintain copy control so that pricing is

not copied from Sales 'rder.

To achieve this, copy the standard pricing to a 6


5/63

/reateB/hange your illing types configuration in $OFA.

Some of the &( stuff are -9

% To bloc3 automatic transfer of the billing document to accounting, mar3 the field.

ndicates whether the system bloc3s automatic transfer of the billing document toaccounting.

During document processing, you can manually transfer bloc3ed billing documents to

accounting by selecting-

Billing 7; Change 7; Release acconting

0% !ccount determination procedure

E% 'utput determination procedure etc. ...

!fter customiGing, use transaction $CH*CK$OFAto chec3 your configuration -9

% #roforma billing types- f it is a proforma billing type, $VT4# :%, the field must

be blan3 and the account determination procedure must be empty.

0% /ancellation billing document types- - ! chec3 is made to see if the cancellationbilling document type has the right VT4#. !n F0 invoice, for e*ample, $VT4# I&I%

can only be canceled with billing type S with VT4# I2I . ! billing type with

VT4# I?I can only be canceled with the VT4# I@I and vice versa.

E% /ancellation billing document type partner functions ! chec3 is made to see if the

cancellation billing document type partner functions are empty or if those that

correspond to the billing type used are empty.

2e*t, ma3e sure that you maintain the copy control for the illing Types-

Sales documents in $TFA

Target Source

e.g. F 9 nvoice '8 9 Standard Sales 'rder

F 9 nvoice 6'8 9 4our Sales 'rder

illing documents in $TFFe.g. (0 9 Debit &emo F 9 nvoice

(0 9 Debit &emo F0 9 nvoice


6/63

Deliveries in $TF)e.g. F 9 nvoice 7F 9 Delivery

F 9 nvoice 6'8 9 4our Delivery

:sually for copy control, you let the rest of the settings remains as S!# defaults.

4ou only assign the new illing Document Types.

!fter that use transaction $CH*CKT$CPFto chec3 your /opy control customiGing.

Billing Bloc/ will not wor/ed i" (o did not assign it

Define the possible bloc3 indicators in #M% 9 $8T$F#

and

allocate them to the billing types concerned in #M%9 $8T$F#P.

4our illing loc3 will not wor3ed if you did not assigned it to the desired billing types.

4ou can auto bloc3 by -9

. sales document type in transaction $O$:, fields illing loc3,

or

0. item categories in #M%9 $8T$AP, by filling the fields illing loc3.

Billing Plan for Milestone BillingMilestone "illing means distri"uting the total amount to "e "illed overmultile "illingdates in the "illing lan.

s each milestone is successfully reached, the customer is "illed eithera ercentage of

the entire ro+ect cost or simly a re)defined amount.

-uring sales order rocessing, the system determines from the itemcategory whether a"illing lan is reuired and, if so, which tye of lan

The tye of "illing lan that is determined at this oint is set u in/ustomi0ing andcannot "e changed in the sales document.


7/63

!illing lans for eriodic "illing and milestone "illing lans forro+ect)related milestone"illing have different overview screens so that you can enter datarelevant to yourrocessing.

1or examle, for milestone "illing, you must "e a"le to enter data toidentify theindividual milestones.

IM2 configuration reuires :)

3. Maintain "illing lan tyes for milestone "illing in OVBO.

4. -efine date descrition in SM30 - V_TVTB.

5. Maintain -ate /ategory for !illing Plan Tye IN OVBJ.

6. llocate date category in SM30 - V_TFPLA_TY.

7. Maintain date roosal for !illing Plan Tye in OVBM.

8. ssign !illing Plan Tye to (ales -ocuments Tye in OVBP.

9. ssign !illing Plan Tye to Item /ategories in OVBR.

. -efine rules for determining the date in OVBS.

Milestone "illing is tyically used for "illing ro+ects, such as lantengineering andconstruction ro+ects. (uch ro+ects often include a series ofmilestones that mar; thecomletion of different stages of the wor;. In the (P %$5 (ystem,milestones are definedin a networ; along with lanned and actual dates for the comletion ofwor;. The milestonesare also assigned to the "illing dates in the "illing lan.

&ach milestone)related "illing date is "loc;ed for rocessing until thePro+ect (ystemconfirms that the milestone is comleted.

-elivery)relevant order items for which a milestone "illing lan aliesare "illed on the"asis of the reuested delivery uantity and not on the total of theconfirmed uantities.

The connection "etween the ro+ect and the sales document item is madein the individualschedule lines of the item. &ach schedule item can "e assigned to anetwor; in a ro+ect.


8/63

To dislay the ro+ect)related data for a schedule line, roceed asfollows:

In one of the overview screens of the sales document, select

3. Item )< (chedule lines.4. Mar; the schedule line and select Procurement details.

The following figure shows an examle of milestone "illing where onlythe /ontract have"een "illed :

Order Item Tur"ine 3==,===

!illing Plan

!illing date -escrition > #alue !illing !loc; Milestone!illing (tatus

=3)3=)?6 /ontract 3= 3=,=== ) x x=3)=5)?7 ssem"ly 5= 5=,=== x x=3)=6)?7 Maintenance 5= 5=,=== x x=3)=7)?7 ccetance 5= 5=,=== x x=3)=8)?7 1inal invoice .. .. x

Networ;$ctivities

Milestone &stimate ctualssem"ly =3)=5)?7 =3)=5)?7Maintenance =3)=6)?7ccetance =3)=7)?7

1or each "illing date in a milestone "illing lan, you can secifywhether the "illingdate is:

3. fixed4. always udated with the actual date of the milestone5. udated with the actual date of the milestone, if the date isearlier than the

lanned "illing date for the date

Billing Plan Fnction and Processing

*.'lain what is Billing Plan0

illing plan processing includes the following functions-

!utomatic creation of billing plan dates

#ricing

illing bloc3

illing inde*

illing status


9/63

illing rule for milestone billing

Fi*ed dates in milestone billing

Document flow

/reating with reference

;*change rate determination

!utomatic /reation of illing #lan Dates

n /ustomiGing for Sales, you control how the system automatically creates the schedule

of dates in a billing plan. The system determines the schedule of individual dates basedon general date information, such as the start and end dates. This general date information

is copied either from contract header data or from proposals in the billing plan type.

Pricing

Sales document items are billed as each billing date in the plan becomes due. The system

determines the amount to be billed either from the condition records that are applicable to

the item or from the values that are e*plicitly entered in the billing plan for a particularbilling date. n milestone billing, for e*ample, you can specify a percentage to be billed

or an actual amount.

Billing bloc/

! billing bloc3 can be set for each date in a billing plan. The bloc3 prevents processing

for a particular billing date but does not necessarily affect any of the other dates in the

plan. n milestone billing, the system automatically sets a billing bloc3 for each billingdate. This bloc3 remains in effect until the proJect system reports bac3 that the milestone

in the corresponding networ3 has been successfully completed. !t this point the system

removes the bloc3.

Billing inde.

For every billing date in a plan, the system creates and updates a billing inde*. f a billingdate is bloc3ed for billing, the system copies this information into the inde*.

Billing stats

The system assigns a billing status to each billing date in the plan. The status indicates to

what e*tent the billing has been processed for that particular date. !fter billing has been

carried out successfully, the billing status is automatically set to K/5. This prevents abilled date from being billed again.

Billing Rle "or Milestone Billing

For every date in the milestone billing plan, you can specify a billing rule. The ruledetermines how the billing amount for the particular date is calculated. For e*ample, you


10/63

can specify whether the billing amount is a percentage of the total amount or whether it is

a fi*ed amount.

n addition, you can specify that the amount to be billed is a final settlement that ta3esinto account billing that has not yet been processed. For e*ample, price changes may ta3e

place after billing dates in the plan have already been processed. The price differencescan be ta3en into account during final settlement.

Final settlement is not automatically proposed in the billing plan by the systemL you mustenter it manually during processing.

Fi.ed dates in -ilestone billing

4ou can control for each date in a billing plan, whether the date is fi*ed or whether the

system copies the date from the planned or actual milestone dates in a proJect.

!oc-ent "low

!fter a particular date in a billing plan is processed for billing, the system updates thedocument flow for the corresponding sales document item.

The document flow for the sales document displays the following data-

/reation date

illing date

illed value

Creating with re"erence

1hen you define a billing plan type in /ustomiGing for Sales, you can enter the number

of an e*isting billing plan to serve as a reference during subsequent billing plan creation.During sales order processing for items that require billing plans, the system

automatically proposes the reference plan and, if necessary, re9determines the billing

dates $based on the current date rules% for inclusion in the new billing plan.

*.change rate deter-ination

n the billing plan with partial billing, you can store a certain e*change rate for each date.The amount billed is the amount determined after using this e*change rate to convert

from the local currency into the document currency.

!n e*change rate can also be stored at item level for the sales document $field- ;*changerate for F on the illing tab page. This fi*ed rate is valid for all dates in the item billing

plan for which no rate is specified in the billing plan. f an e*change rate is entered both


11/63

for the date in the billing plan and at item level in the e*change rate field, then the system

uses the rate specified for the date during billing.

f no e*change rate is entered for the the date or at item level, then the system uses thee*change rate used for invoice creation and it is forwarded to F.

'hen using a header "illing lan, all "illing lans lin;ed to thisheader "illing lan are automatically udated. If, for examle, youenter an exchange rate manually for the first date in the header "illinglan, this is automatically coied to the corresonding dates for theitem "illing lans.

#AP Billing 7 Co-bine Billing "or deli6eries with

di""erent date

1hen using transaction $F%&or illing $bac3ground%, the date of the billing document

$e.g. the current date% must be entered $n $F%&- settings, default data.%

n $F%


12/63

n tr* VTF! $if your billing is sales order based% choose your billing type and S' type,

there select your item categories and there select the field V8"BV8# data. n that field

you will see the currently used routine. 1ith the help of your !!# guy create a copy ofthat routine under a different number and add your lines of code. 7etIs say you use

routine AA.

F'8& D!T;2="'#;8;2=AA.

M Header data

M V8"9***** ............

M tem dataM V8#9***** ............

M !dditional split criteria

D!T!- ;(2 'F 6:",

&'D:7$E% V!7:; IAAI,

VT1;( 7"; V!"9VT1;(,S#!8T 7"; V!"9S#!8T,

;2D 'F 6:".

6:"9S#!8T V!"9S#!8T.6:"9VT1;( V!"9VT1;(.

V8"96:"8 6:".

;2DF'8&.

This is how it should loo3 after modification-

M Header data

M V8"9***** ............

M tem data

M V8#9***** ............M !dditional split criteria

D!T!- ;(2 'F 6:",

&'D:7$E% V!7:; IAAI,

VT1;( 7"; V!"9VT1;(,S#!8T 7"; V!"9S#!8T,

#ST4V 7"; V!#9#ST4V, N9 2ew line

;2D 'F 6:".

6:"9S#!8T V!"9S#!8T.

6:"9VT1;( V!"9VT1;(.


13/63

6:"9#ST4V V!#9#ST4V. N9 2ew line

V8"96:"8 6:".

;2DF'8&.

!fter this routine is created and activated place it as the default copy control routineinstead of the old ones.

Ma.i-- n-ber o" ite-s in F= reached Message no0

F4 292

f you hit the above erros when you create an invoice in SD, the corresponding

accounting document is not created.

The error is as follows-

&a*imum number of items in F reached &essage no. F4 292

!iagnosis

The ma*imum number of items for an F document $IOOOI% has been e*ceeded.

#(ste- res'onse

F documents have a E9digit item counter that limits the number of items permitted per

document.

Procedre

f the documents with an e*cessive number of items come from another application area$e.g. sales, logistics, order accounting%, you can configure the system to the effect that

these documents are summariGed in F.

How could this error be solved as none of your invoices are getting accounted in FP

To overcome this, the only way was to brea3 the accounting invoices, with O?A items

and the other with the rest.

Pre'aid 'rocess 'ossible

99999'riginal &essage99999SubJect- #repaid process possible

am loo3ing for information on how we could implement a prepaid process. y prepaid

process mean-

9 /ustomer sends to us his order9 f customer is set as prepaid, we produce an invoice for him to pay


14/63

9 'nce we have received his payment, we release the sales order for delivery

9 no further billing document is produced.

found information in online documentation about down payments $ imagine that ourprepaid process could be a AAQ required down payment% but it does not seem that it

would wor3. From what understood it loo3s li3e the billing plan is handled based uponthe

item category, which implies the processing is material specific not customerspecific.

1hat we do now-

9 1e have defined a ris3 category prepaid which is assigned to our prepaid customer.This ris3 category automatically bloc3 the sales order for delivery.

9 1e receive the sales orders and produce a #ro Forma invoice from it, and send it to

customer

9 'nce we receive the payment, we release the sales order for delivery and produce the

invoices.9 1e post the payment we received earlier against this last invoice.

!s you see, this requires a lot of manual wor3 and a lot of time is wasted to match all

documents together. There most be a more efficient way to handle this, anybody have any

hintsP

999998eply &essage99999SubJect- 8;- #repaid process possible

Hi againR

4ou are rightR However, if you create a new item category for the prepaid scenario, you

can

select what item category $and process% to use at order entry. t is also possible to code auser e*it so that only certain customers will get the prepaid process. This can be done also

with item category groups $can be used to determine what default item category thatshould appear%. This would mean that you either have different materialnumbers for the

different processes or use different distribution channels in the sales order. D/ A could

be

the normal process and D/ 0A the prepaid process. Then you need to create the salesviews in material master for D/ 0A for all materials that should be possible to run in the

prepaid scenario, and enter the prepaid item category group in the sales item category

group field in material master.

Here is a proposal of customiGing activities to achieve this-

. /reate a new item category as a copy of the normal item category used for non9prepaid


15/63

sales. $/hange the billing in the item category to order related billing with no billing

plan%

0. /reate a new item category group 6


16/63

4ou must also go to copying control for orderBdelivery to billing document at item level

under Data V8"BV8# and maintain routine AA@ individual invoice limited or a

similar routine that accesses the data maintained here

!oc-ent Not Rele6ant For Billing

How to resol6e !oc-ent not rele6ant "or billing error -essage>

/hec3 the detailed error log in VFA screen. 1e may get more information on error.

Then, chec3 have you completed the #( for the delivery document or not.

2e*t, go to that tem /ategory functionality V'VC and find if it is order or deliveryrelated billing.

!nd after that go and chec3 in the particular Sales order document type whether billing

document types are maintained in the sales document or not.

f every thing is correct go and find with copy controls

f it order related, go VTF!f it Delivery related, go VTF7 and chec3 in your document type combination is

maintained or not, if they are maintained item category is available or not.

A"ter deli6er( while creating billing doc-ent s(ste- showing error that no billing

doc-ent is generated "or -aterial no +40 #o how = can sol6e this isse0

/hec3 if tem /ategory is chec3ed for illing or not.

Nor-al #ales Order C(cle17

#te' 31 #ales !oc-ent T('e

&( Sales and Distribution Sales Sales Documents

Sales Document Header-. Sales Document Type-The sales document types represent the different business

transactions, such as nquiry, uotation, Sales 'rder, etc. To create new sales order type,

always copy as with reference to similar sales order. f possible use standard sales order.0. Define 2umber 8anges For Sales Documents- &aintain number range with discussion

with core team.E. !ssign Sales !rea To Sales Document Types-

!. /ombine sales organiGations B /ombine distribution channels B /ombine divisions-;nsure to maintain these, else Sales 'rder creation will give error.

. !ssign sales order types permitted for sales areas- !ssign only required Sales 'rder

Types to required Sales !rea. This will minimiGe selection of Sales 'rder Type as persales area.


17/63


18/63


19/63

Table- V8"

Field- V8"96:'28 9 !ssignment $this field lin3 the original and cancelled billing

documents%

/ancel billing documents must be successfuly released to accounting. :sually it failedwhen user tried to cancelled current period with previous date.

#chedle $F%& For =ndi6idal Billing Rn

#AP Fnctional; #! =n #AP

How to schedle billing to be rn ato-aticall(>

4ou can create individual illing documents in VFA>, with out any saving of each and

every billing document.

Select all the deliveries which you want to create billing documents, using /ntr utton,

and clic3 on individual billing. Then all the deliveries will go for billing individually in a

single run. !nd you can also see all the billing documents numbers, which are created.2o need to select single delivery each time.

f you want to do a batch Job for billing, proceed for the following process

. goto VFA>, in the selection screen Delivery document range, for which you want to

create billing documents e.g., in SD Document field, give delivery to A.

0.2ow /lic3 on ('T' 9 Variant 9 Save as Variant, then it will ta3e you to anotherscreen, give the variant name, e.g., test, and save it.

E. goto S&E@, this is used to do batch Job, if you dont 3now any thing also, you can do

the entire process, using ' 16!8D, clic3 on ob 1iGard which is on the screen.

>. t will ta3e you to different steps, Just you need to give your variant name, $in Job namefield% $in the first screen% the continue for further steps, n the !!# #rogamme 2ame

give SD77D7, $this is the programme used to create billing documents% continue to

give the specified time which you want to run this batch Job, li3e immediate, after an

hour, or a specific day li3e so.

?. /ontinue further to complete the tas3, now you batch Job will run at a specified time

which you mentioned, if you mentioned as immediately, then once you comple this

process, your vairant will run, and billing documents will be created.

@. #lese ensure that all the deliveries are perfect, meaning there is no billing bloc3 or anything.
http://www.sap-img.com/index.htmhttp://www.sap-img.com/sap-sd.htmhttp://www.sap-img.com/sap-sd.htmhttp://www.sap-img.com/index.htmhttp://www.sap-img.com/sap-sd.htm


20/63

4ou can chec3 the status of your batch Job using t. code S&EC.

!i""erence between the R#NA#T%% and #!B=))!) 'rogra-0

8S2!STAA is a program which is related to output related activities. :sing this program,we can schedule the creation of outputs $#DFs, email etc% in total for any document

created in any of the applications. The details are read and stored in the database table

2!ST. The same program is customised for each applications using programs li3eSDCA!V! which are also used for the same purpose but only for sales orders.

SD77D7 is the program for illing due list. This program finds out all the orders or

deliveries or both which are due for billing and it will trigger the billing creation. t reads

tables li3e V!", V!#, V:", V:#, 7"#, 7#S etc and the created billingdocuments are stored in tables V8", V8#.

*.'lain The Conce't o" Resorce Related Billing

Please e.'lain to -e the conce't o" resorce related billing and its

di""erent between 'eriodic and -ilestone0 =n what /ind o" bsiness scenario do we

se it> and what are the settings reired to se it>

#eriodic billing is used when you want to bill the customer at different points of time

based on the periodicity or progress of the wor3.

&ilestone billing can be used for this type of billing purposes when you want to have

billing control from the proJect.

8esource billing is based on the resource consumption for the particular activities.

Dynamic tem #rocessor $D#% profile is used for the resource related billing.

Steps to be followed-

% /onfigure D# #rofile $T.code 'D#%

0% Specify the usage 9

$i% illing 8esult !nalysis $88%

$ii% 8equest uotation $Sales #ricing%

E% Specify 9$i% Sales Document Type $#S0%

$ii% SD Doc Type /&8

>% n Sales 'rder Type 99 Sales 'rder /ategory 9 7 $Debit &emo 8equest%

?% Document #ricing #rocedure 99 #S $/ustomer #roJect%


21/63

@% Select the billing usage and clic3 on characteristics. eg99 !ctivity Type

C% Then define sources. Select !ctual /ost as we use actual cost for 88. DefineQ

W% Sources 99 Selection /riteria- This would display all characteristics. 2ow in !ctivity

Type 99 &ention the activity type

O% f more activity type are being used then create set of activity type using T.code (SA

A% &aterial Determination 99 nitially create material with &aterial Type Service

% The service material should be mentioned in the material determination

0% /riteria 99 n criteria allocate the activity type for the specific material. $1e can also

use cost element, cost center, which we have defined in characteristics%

E% /reate #roJect $T.code /0A2%

>% /reate Sales 'rder $T.code V!A%

?% oo3 /!TS

@% ;*ecute D#O to view Sales #ricing

Co--on *rrors1

A!%373441 *rror dring -aterial deter-ination "or sales doc-ent ite-0 Material

Origin "ield was not chec/ed in the Costing tab o" the -aterial -aster0=D7%421 No cost -anage-ent is 'ro6ided "or sales doc-ent ?contract@ ite-0 This is

sall( becase there is no reire-ents t('e assigned to the contract ite- ?see

'rocre-ent tab@0

No -aterial a''ears in !MRECMR0 =n the -aterial -aster costing 6iew, set the

Material Origin chec/bo. ?see O## note 32&:9@

No e.'enditre ite- "ond0

(o bac3 to the service order and chec3 there are actual costs

/hec3 your D# #rofileL specifically the sources section to ensure you are not filtering

out any dynamic items.

/' /onfiguration-

"7AE- /hec3 activity type validity dates

"!AE- /hec3 cost element validity dates


22/63

"!AE- For labour, chec3 cost element category is >E

"!AE- /hec3 if 8ecord qty flag is set on ndicators tab

"!AE- /hec3 cost element assigned to your controlling area

"#0@- /hec3 that activity type is lin3ed to cost centre

"#0@- /hec3 that there is a rate for the activity typeBcost centre

"#0@- /hec3 are you using the correct version

Cancelled Billing !oc-ent Has No Acconting

!oc-ent

Real #! #''ort estion1= ha6e cancelled a billing doc-ent throgh 6"330 That -eans the cancellation

billing doc-ent did not generate acconting doc-ent0 Where to chec/ed>

1hen you cancel a billing document, you are actually creating a cancellation document.The cancellation document copies data from the billing document and transfers an

offsetting entry to the accounting department.

So once you cancel the billing document it will create one cancellation Document and

one reversal !ccounting Document.

There is no need to cancel !ccounting document which is created after cancel a billingdocument.

7ets handle it phase by phase.

First Scenario

4our accounting document not generated,

. VFA0 &ode /lic3 )8elease to !ccounting the !ccounting documents not generated.

0. f yes, then '" ;lse

E. /hec3 1hether you have assigned !ccounting 3eys to the relevant condition types.

>. /hec3 !ccount assignment #rocedure V"'! and chec3 (B7 account has been

assigned.

?. f error found correct it ;lse


23/63

@. /hec3 with F /onsultant whether !ccounting entries has been posted with reference

to customer and nvoice.

Second Scenario

f accounting documents gets generated and you use VF to /ancel the invoice, thenautomatically the posting document gets reversed and separate number will be assigned

for those documents. This you can see in the document flow. /hec3 with F /onsultant.

#lease /hec3 this -

S#8'999Sales and Distribution99illing Documents99Define illing Types

Select illing type S.

Then chec3 #osting loc3, it should be unchec3ed.

/hec3 whether for the S billing document type #osting bloc3 has been chec3ed or not. f

it has been chec3ed then unchec3 it and secondly also chec3 in the F0 billing document

type whether S cancellation billing document type has been assigned or not.

1inally chec; whether the "illing document which you were cancellingthat "illing document generated accounting document or not. If it hasnot generated the accounting document then chec; the settings in O!9

How To !o Con"igration For Credit Manage-ent

/redit and ris3 management ta3es place in the credit control area. !ccording to yourcorporate requirements, you can implement credit management that is centraliGed,decentraliGed, or somewhere in between.

!n organiGational unit that represents the area where customer credit is awarded and

monitored. This organiGational unit can either be a single or several company codes, if

credit control is performed across several company codes. 'ne credit control areacontains credit control information for each customer.

For e*ample, if your credit management is centraliGed, you can define one credit control

area for all of your company codes.

f, on the other hand, your credit policy requires decentraliGed credit management, youcan define credit control areas for each company code or each group of company codes.

/redit limits and credit e*posure are managed at both credit control area and customer

level. 4ou set up credit control areas and other data related to credit management in

/ustomiGing for Financial !ccounting. The implementation guide is under ;nterpriseStructure 9 Definition or !ssignment 9 Financial !ccounting and then &aintain credit


24/63

control area. 4ou assign customers to specific credit control areas and specify the

appropriate credit limits in the customer master record.

Ti's b( 1 Ka'ilaa

Settings for determining the credit control area of a document. The settings of items 9 >are ta3en into account according to their priority. The credit control area found is stored

in field V!"9"";8.

. Transaction OB:

/hec3 which credit control area is assigned to the company code./ompany code-

/redit control area-

0. Transaction O$F)

/hec3 which credit control area is assigned to the sales area.

Sales area-/redit control area-

E. Transaction D!%9or $!%9/hec3 which credit control area is assigned to the payer.

#ayer-


>. Transaction #*2s user e*it ;?"=AA being usedP

?. Transaction OBKFor the settings under items 0 9 >, field !ll company codes must be mar3ed in

Transaction

OB&4, or the credit control area must be entered under the relevant company code in

table

TAA/& of the credit control areas allowed./ompany code-

/redit control areas allowed-

@. Settings for the credit chec3s

C. Transaction O$AK1hich settings do e*ist for the sales document type usedPSales document-

/hec3 credit-

/redit group-

W. Transaction O$A!1hich settings do e*ist for the delivery type usedP


25/63

Delivery type-

/redit group for delivery-

/redit group for goods issue-

O. Transaction OB%3

/redit managementB/hange ris3 categoryDefinition of the ris3 category for each credit control area. This ris3 category can be

assigned to a credit account by using Transaction F!9.

A. Transaction O$A:

Here, the individual credit chec3s for 3ey fields

o credit control areao ris3 category

o credit group are set. Ta3e these 3ey fields from the above settings and go to the detail

screen. n particular, chec3 whether fields 8eaction and StatusBbloc3 are set

correctly. To carry out follow9up actions in case of a credit bloc3, the credit chec3status must be set $field StatusBbloc3%.

. Transaction F!9

/redit master data for the payer of the relevant document./redit account-

/redit limit-

8is3 category-/urrency-

0. Settings for updating the credit values :pdate of the credit values is required for the

limitchec3 $static or dynamic credit limit chec3%.

E. Transaction O$A2

:pdate of the credit value is active for the corresponding item type if the chec3 bo* is

mar3ed. This field corresponds to

field !ctive receivable in Transaction $O$2.tem type-

!ctive receivable-

>. Transaction $E%:, #ricing

n the pricing procedure used for pricing, subtotal ! must be entered in a line fordetermining the credit value $mar3 the pricing procedure and doubleclic3 on

/ontrol%.

:sually, the net value plus ta*es is used. This way the system is determined to use thissubtotal for credit pricing. The credit price is stored in field V!#9/ and used

for

update and credit chec3.4ou can find the used pricing procedure of the order under tem 9 /ondition 9


26/63

!nalysis.

#ricing procedure-

7ine with subtotal I!I-

?. Transaction OB&4

1hich update group $field :pdate% do you use in the relevant credit control areaPThe

default setting is 0. f you use another update group, chec3 whether this is fine withyou. f you open an 'SS message, please tell us the alternative update group.


:pdate-

@. Transaction OMO3

1hich 3ind of update did you choose for structure SA@@P

n any case, Synchronous update $% has to be chosen as the 3ind of update.

!ll other settings will lead to errors.

MRP bloc/ "or Credit li-it attained Csto-ers

How to bloc/ the reire-ent ?M!%&@ generated b( the ite- categor( in a sales

order when the csto-er has attained the credit li-it> The MRP reire-ents still

a''ear e6en thogh the schedle is ero0

4ou should try and use one of the standard requirements.

See in transaction $OFM.

5nder Reire-ents E #bseent Fnctions E Res0A6ailablit(0

Try using rotine 3%, you may have to twea3 if it doesnIt wor3 e*actly as youId li3e.

For e*ample, you can write a rotine +%because you only wanted this reaction for

certain business units. rregardless, using a routine similar to this will prevent therequirement froma''earing in M!%& "or orders bloc/ed on credit .

/ode-

D!T!- 1=6SD/8D T4#; 6SD=/8;DT7/".

D!T!- 1=/&(ST 7"; V:"9/&(ST.

S;7;/T S2(7; M 2T' 1=6SD/8D

F8'& 6SD=/8;DT7/"

1H;8; "";8 V!"9"";8!2D /T7#/ V!"9/T7#/.

F S49S:8/ A !2D V:"9/&(ST /! II.


27/63


28/63

999998eply &essage99999

SubJect- 8e- /redit &gmt Dynamic chec3ing

From- 7eslie #aolucci

1e chec3 credit at the time of the delivery $at delivery creation and before pic3ing% and

use the bloc3ed sales doc processBlist to release them. This can be set up in customiGingunder ris3 management9 credit management.

99999;nd of 8eply &essage99999

#ales 6ale "ield in not getting 'dated a"ter creating

the billing

99999'riginal &essage99999

SubJect- Sales value field in not getting updated after creating the billing

we are on >.@b. we are going for credit management but facing one problem. in fdE09

customer credit management change 9 the sales value feild in not getting updated after

creating the billing.eg. when i create the order 9 the order value get updated in the sales value in fdE0. after

creating the delivery 9 that value remains same in the feild of sales value. but when i am

going for billing $delivery related%, the bill value is appearing in IreceivablesI but the

amountin Isales valueI is not getting reduced. because of this the credit e*posure is increasing

continuously.

update group for corrosponding credit ctrl area is 0. also the item is mar3 for credit

update.can anyone tell the missing lin3P

than3ing in advance

999998eply &essage99999SubJect- 8;- Sales value field in not getting updated after creating the billing

Hi,

4ou need to chec3 couple of settings li3e-

. 4our customer should be assigned the credit control area.

0. n your tem /ategory /redit should be active.

8egards,


SubJect- 8;- Sales value field in not getting updated after creating the billing


29/63

customer is assign to concorn //! and item category is mar3 for credit active


SubJect- 8;- Sales value field in not getting updated after creating the billing

Hi,

/hec3 the credit update group in the transaction '>?. The credit update group controls

when the values of open sales orders, deliveries and billing documents are updated. t

should be IAAAA0I.

Further also refer to the 'SS note W@E.

Have fun

99999;nd of &essage99999

!i""erence Between #i-'le and Ato-atic Credit

Chec/ T('es

*.'lain in detail di""erence between si-'le and ato-atic credit chec/ t('es0 =n

ato-atic chec/, di""erence between static and d(na-ic chec/s0

#=MP)* CR*!=T CH*CK 1Tr./ode 9 FDE0

t /onsiders the Doc.Value U 'pen tems.

Doc.Value - Sales 'rder Has been saved but not delivered

'pen tem - Sales 'rder has been saved , Delivered, illed Transfered to F, but notreceived the payment from the customer.

;g- /ustomer /redit 7imit is 8s.,AA,AAAB9

Suppose Doc.Value U 'pen tem Value is 8s.,A,AAAB9

Here credit limit e*ceeds then system reacts.

'ptions - !% 1arning &essage% ;rror &essage $Sales 'rder wonIt be saved%

/% ;rror &essage with Delivery loc3

A5TOMAT=C CR*!=T CH*CK 1(ive e*tra credit facilities to the particularcustomer.


30/63

ST!T/ /8;DT 7&T D;T;8&2!T'2 -/hec3ing (roup U 8is3 /atageory U

/redit /ontrol !rea.

!% /redit /hec3ing (roups - Types of /hec3ing (roups.

A% SalesA0% Deliveries

AE% (oods ssue!t all the above E levels orders can be bloc3ed.

% 8is3 /atageory - ased on the ris3 catageories company decide how much credit has

to give to the customer.

H(H 8S" $AAA% - 7'1 /8;DT7'1 8S" $AAA0% - &'8; /8;DT

&;D:& 8S"$AAAE% - !verage /redit

Static /redit /hec3 it chec3s all these doc value chec3 with the credit limit

% 'pen Doc.Value B Sales 'rder Value - 1hich is save but not delievered

0% 'pen Delivery Doc.Value - 1hich is delivered but not billed

E% 'pen illing Doc.Value - 1hich is billed but not posted to F

>% 'pen tem - 1hich is transfered to F but not received from the customer.

D42!&/ /8;DT /H;/" - % 'pen Doc0% 'pen Delivery

E% 'pen illing>% 'pen tems

?% HoriGon #eriod ;g.E&onths

Here the System will not consider the above ,0,E > values for the lost E months

Then assign the Sales Doc Del Documents.

Sales Doc.Type$'8% U credit /hec3$A% U /redit (roup $A%

/redit 7imit /hec3 for Delivery Type - Del.Type $7F% U Del /redit

(roup $A0% U (oods ssue /redit (roup $AE%

Ti's b( Ch0I0RaJase/ahar

#et 5' "or Credit Card Pa(-ent Processing


31/63

(iven below is the set up for credit card payment processing-

Set :p /redit /ontrol !reas-

Define /redit /ontrol !rea

Transaction- '>?Tables- TA>

!ction- Define a credit control area and its associated currency. The :pdate (roup

should be KAAA05. This entry is required so the sales order will calculate the value toauthoriGe

!ssign /ompany /ode to /redit /ontrol !rea

Transaction- 'EW

Tables- TAA!ction- !ssign a default credit control area for each company code

Define #ermitted /redit /ontrol !rea for a /ompany/ode

Transaction-Tables- TAA/&

!ction- For each company code enter every credit control area that can be used

dentify /redit #rice

Transaction- VBAWTables- T@WES

!ction- Towards the end of the pricing procedure, after all pricing and ta* determination,

create a subtotal line to store the value of the price plus any sales ta*. &a3e the

following entries-Sub to- )!+

8eqt- )0+!lt/Ty- )>+

!utomatic /redit /hec3ing

Transaction- 'V!W

Tables- T@OF!ction- Select each combination of credit control areas, ris3 categories and document

types for which credit chec3ing should be bypassed. 4ou need to mar3 the field )no

/redit /hec3+ with the valid number for sales documents.

Set :p #ayment (uarantees

Define Forms of #ayment (uaranteeTransaction- 'VFD

Tables- T@O"

!ction- 8BE is delivered with form )A0+ defined for payment cards. 'ther than thedescriptor, the only other entry should be )E+ in the column labeled )#ymt(ua/at+


32/63

Define #ayment (uarantee #rocedure

Transaction-

Tables- T@O&BT@O'!ction- Define a procedure and a description.

Forms of #ayment (uarantee and ma3e the following entries Sequential 2umber )+

#ayment (uarantee Form )A0+8outine 2umber )A+ 8outine 2umber can be used to validate payment card presence.

Define /ustomer #ayment (uarantee Flag

Transaction-

Tables- T@O#!ction- Define a flag to be stored in table.

/reate /ustomer #ayment (uarantee )#ayment /ard #ayment /ards $!ll /ustomers

can use #ayment /ards%+.

Define Sales Document #ayment (uarantee Flag

Transaction-Tables- T@O8

!ction- Define the flag that will be associated with sales document types that are relevantfor payment cards

!ssign Sales Document #ayment (uarantee Flag

Transaction-

Tables- TV!"!ction- !ssign the document flag type the sales documents types that are relevant for

payment cards.

Determine #ayment (uarantee #rocedureTransaction- 'VFTables- T@O:

!ction- /ombine the /ustomer flag and the sales document flag to derive the payment

guarantee procedure

#ayment /ard /onfiguration

Define /ard Types

Transaction-

Tables- TV/2

!ction- /reate the different card types plus the routine that validates the card for lengthand prefi* $etcZ%

Visa , &astercard, !merican ;*press, and Discover

/reate the following entries for each payment card!&;< !merican ;*press 6//!8D=/H;/"=!&;< &onth

D/ Discover /ard 6//!8D=/H;/"=D/ &onthMMMMM

&/ &astercard 6//!8D=/H;/"=&/ &onthVS! Visa 6//!8D=/H;/"=VS! &onth


33/63

The 8outines can be created based on the original routines delivered by S!#.

MMMMMS!# does not deliver a card chec3 for Discover /ard. 1e created our own routine.

Define /ard /ategories

Transaction-Tables- TV/T4

!ction- Define the card category to determine if a

payment card is a credit card or a procurement card./reate the following two entries

/at Description 'ne /ard !dditional Data

// /redit /ards 2o9chec3 2o9chec3#/ #rocurement /ards 2o9chec3 /hec3

Determine /ard /ategories

Transaction-

Tables- TV/TD!ction- For each card category map the account number range to a card category.

&ultiple ranges are possible for each card category or a mas3ing technique can be used.

(et the card number ranges from user community. elow is Just a sample of what am

aware are the different types of cards.

Visa /redit ;*pires in C days.

>AAAAA >A??AA

>A??A? >A??>O>A???? >?O0C

>?O0O >0>@AE

>0>@A@ >0C?E0>0C?E> >0WCOO>0WOAA >C@OO

>CCAA >OOOOO

Visa #rocurement ;*pires in C days.>A??A >A??A>

>A???A >A???>

>?O0W >?O0W>0>@A> >0>@A?

>0C?EE >0C?EE

>0WWAA >0WWOO

&astercard /redit ;*pires in EA days?AAAAA ?>A>OO

?>A@AA ??>OOO

??CAAA ?OOOOO&astercard #rocurement ;*pires in EA days

?>A?AA ?>A?OO

???AAA ??@OOO


34/63

!merican ;*press /redit ;*pires in EA days

E>AAAA E>OOOO

ECAAAA ECOOOO

Discover /ard /redit ;*pires in EA days

@AAA @AOO

Set Sales Documents to accept #ayment /ard nformation Transaction-

Tables- TV!"!ction- 8eview the listing of Sales Document types and enter )AE+ in the column labeled

)#T+ for each type which can accept a payment card

/onfiguration for !uthoriGation 8equest

&aintain !uthoriGation 8equirements

Transaction- 'VO!

Tables- TF8&!ction- Define and activate the abap requirement that determines when an authoriGation

is sent. 2ote that the following tables are available to be used in the abap requirement$V!", V!#, V"D, V:", and V:#%.

Define /hec3ing (roup

Transaction-

Tables- //#(!!ction- Define a chec3ing group and enter the

description. Then follow the below guidelines for the remaining fields to be filled.

!uth8eq 8outine OA is set here.

#re!u f chec3ed 8BE will request an authoriGation for a .A and the authoriGation will beflagged as such. $nsight does not use pre9authoriGation chec3%.

! horiGon This is the days in the future S!# will use to determine the value to authoriGe$nsight does not use auth horiGon period%.

Valid 4ou will get warning message if the payment card is e*piring within EA days of

order entry date.

!ssign /hec3ing (roup to Sales DocumentTransaction-

Tables- TV!"

!ction- !ssign the chec3ing group to the sales order types relevant for payment cards

Define !uthoriGation Validity #eriodsTransaction-

Tables- TV/2

!ction- For each card type enter the authoriGation validity period in days.

!&;< !merican ;*press EAD/ Discover card EA


35/63


36/63

*.'lain abot dnning 'rocess in credit -anage-ent>

7et me e*plain in simple terms-

% 4ou have a /ustomer which you had felt, he is doing good business and supplied

material on /redit of >? days.

0% Since this customer is good as you felt, you have not managed /redit /hec3s as well.

So, he had comfortably reached to the fullest credit $or even more% which you can afford

for any customer.

E% 'ne fine day you got realised that, there is very bad debt with this customer and needto recover from him and till then, there will be no further supply to the customer.

>% 4our companyIs legal department has laid a policy that, inorder to recover any bad

debts, li3e-

a% 1e will send a normal payment reminder.b% n case customer doesnt respond, we will send at least further reminder $dunning

notice% may be O times

$O reminders% $Dunning level% and what intervels of time $dunning frequency%c% Still if the customer doesnt resopond for the reminders, you will file a law suit against

the customer for recovering

the #ayments.

d% Finally, after getting veridict, you may proceed for auction of his property or as per theorder for 7aw.

2ow in S!#, the definition of Dunning procedure is a pre9defined procedure specifying

how customers or vendors are dunned.

For each procedure, the user defines9 2umber of dunning levels

9 Dunning frequency

9 !mount limits9 Te*ts for the dunning notices

n S!#, you will maintain the Dunning #rocedure at customer master. 8eferring to this

your SD Team B F Team $user team% will effect Dunning

#S- 4ou might remembered the dunning procedure laid by 8elaince &obile, sometimebac3, sending street rowdies for recovering the bad debts from users. That is dunning.8emember 8eliance, you will not forget dunning forever.

What =s Credit *.'osre

What do (o -ean b( credit e.'osre>


37/63

They are the transactions with a customer that are relevant for credit limits on a specified

date.

The credit e*posure is updated based on the update algorithm assigned to the creditcontrol area.

AAAA0 9 updated at Sales 'rder

AAAA? 9 updated at Delivery

AAAAW 9 updated at illing

To loo3 at only 8eceivables for a customer loo3 in FDE0. f you have bad data run thereorganiGation program through S;EW.

/hec3 2ote >0??0E 9 /ollection of consulting notes- /redit update and related.

Surely you must run report 8V"8;DCC $2ote >AAE 9 8V"8;DCC- 8eorganiGation

credit data, new documentation and related will help you%.

30 How is credit e.'osre calclated ?seen in F!9@>

t5s simple summation of 8eceivables U Special liabilities $li3e down payments, advance%

U Sales value

90 =" 5'date%%%%39 in CCAr then on creating #ales Order, the e.'osre increases

b( #O 6ale0

Bt i" 'date%%%%34, then also on creating #ales Order, the e.'osre increases b(

#O 6ale0

=s this correct>

thin3 in case of AAAA? 'pen sales order values should not be considered.

0 What role e.'osre 'la( in the credit -anage-ent 'rocess0 = -ean does the

s(ste- -atch the 6ale o" credit e.'osre with credit li-it to "ind that it is e.ceeded

or it does it di""erentl(>

/redit e*posure is in fact the main player. n credit management if the customer5s creditlimit is AAAA and credit e*posure is OOAA then customer can only be able to buy now

worth of AA only. t5s the credit e*posure which should not crossed over the credit limit.

For reporting purpose, where we can get customer credit e*posure which showing in

FDE0.

(o to t.code F.E for an overview of the credit e*posure, and also you can uses=!78=WCA000W to overview the credit e*posure.

#AP #! C=N Con"igration


38/63

y Shesagiri

What is C=N>

/2 &eans /ountry ndia Version

n ndian Ta*ing procedure, ;*cise Duty plays a vital role in manufacturing cenario5s.;*cise related configuration is 3nown as /2 configuration. /2 /onfiguration is a topic

in itself.

Some info on /2 /onfiguration $it may not appear as understandable below, but if you

chec3 on screen, it will be understood better%

/ountry Version ndia comes with four pricing procedures as follows-

9 2F!/ $Sales from manufacturing plants%

9 2;


39/63

ndicator for confirming, !;D usage !dditional ;*cise duty #ercentage.

These are livable under the additional duties of e*cise act. These duties are in addition to

basic e*cise duty and special e*cise duty. ;*ample 9 !dditional ;*cise duty is livable incase of te*tile products, tobacco and sugar.

Similarly for S;D /;SS 2umber of tems in ;*cise nvoice Shows the ma*imumnumber of line items that the authorities allow per e*cise invoice.

Dependencies 9 This information is used when you create an e*cise invoice in Sales andDistribution $SD% for factory sales and for other movements. This information is used to

split the transfer postingsI items into multiple subcontracting challans.

;*cise register set description- Description of the e*cise registers set.

#artial /;2V!T /redit- ndicates that the e*cise registration D is allowed to credit only

a portion of its input e*cise duty to its /;2V!T account

Dependencies 9 1hen you post a goods receipt, the system splits the input e*cise duty on

the material into its deductible and nondeductible amounts. t posts the deductible duty to

the appropriate /;2V!T account, and adds the nondeductible duty to the material value.

This information is also shown when you post the vendorIs e*cise invoice.

&aintain /ompany /ode Settings.n this &( activity, you maintain the data relating to your company codes.

Document Type for /;2V!T #ostings.

t controls, which document type the system uses when ma3ing /;2V!T postings inFinancial !ccounting $F%. Here ;D is document type for cenvat posting.

ndicator for providing debit account overwriting

Debit !ccount 'verwrite ndicator. < 9 ndicates debit accounts can be overwritten. :se

n e*cise Journal voucher transaction. t provides the fle*ibility to the user to enter thedebit account of his choice depending on the nature of transaction.

!utomatic balance ndicator 9 ;*cise year start month. The calendar month mar3ing the

beginning of the e*cise year. This start month represents the month for the start of the

e*cise invoice number range. The month A> is entered here indicating !pril of the

calendar year as the start month for e*cise invoices. !ny change by the ;*cise authoritiesregarding start month should be ta3en care of by an entry in this field and initialiGation.

;*cise invoice selection procedure -;*cise invoice selection type. To indicate the method

opted by the company for selecting the e*cise invoice. t can be either earliest or latestinvoices that were received. 2umber of e*cise invoices to be selected ndicates the

number of e*cise invoices that needs to be selected in the e*cise invoice selection.


40/63

Days to be considered for e*cise invoice selection 2umber of days from document date

for e*cise invoice selection.

;*ample 9 f the value of this field is 0A and today is 0W9AE9OC. The e*cise invoiceselection will show the related invoices only for the period AW9AE9OC to 0W9AE9OC.

Document type for TDS F posting- Financial accounting document type for TDSposting.

Document type for F posting on :tilisation Financial accounting document type for TDSposting.

ndicator for item level e*cise duty round off 9 This indicator is to be used for deciding

whether tem level e*cise

duty amount rounding off is required during procurement cycle. f mar3ed I


41/63

9 Specify whether it is a manufacturing site or a depot.

9 !ssign it an e*cise registration D. 9 4ou can assign the same D to more than one plant,

if required.

Depot 9 ndicates that the plant in question is a depot. 9 Depots are required to prepare

register 8( 0ED, and follow different procedures for goods receipt and invoicegeneration.

9 2umber of goods receipt per e*cise invoice.9 &ultiple (8 for one e*cise invoice, Single credit

9 &ultiple (8 for one e*cise invoice, multiple credit

&aintain ;*cise (roups 9 n this &( activity, you define your e*cise groups. For eache*cise group, you can also control how various e*cise invoice transactions will wor3.

;*cise (roups 9 n this activity, you define e*cise groups. !n e*cise group allows you to

maintain a separate set of e*cise registers and e*cise accounts. The 8( 0E!, 8( 0E/ and

#7! serial numbers are created for an e*cise group.

8ecommendation 9 :nder normal circumstances, e*cise authorities require everybusiness to maintain only one set of e*cise registers and one set of accounts. ut through

e*emption from the authorities, multiple boo3s can be maintained.

f your company has only one set of e*cise registers, then you need to maintain only one

e*cise group.. /reate one e*cise group for each set of registers that you need to 3eep.

0. !ssign the e*cise groups to plants.

E. &aintain whether this ;*cise group is for a depot or not.

f you receive only one consignment for an ;*cise challan then you can leave (8Is per ;as blan3. f you receive multiple (8Is for a given ;*cise challan and would li3e to avail

multiple credit mar3 the (8s per ; as I&ultiple (8Is for one e*cise invoice, multiplecreditI. !lternatively if you want to availa the credit only after all the goods receipts

have been made mar3 it as I &ultiple (8 for one e*cise invoice, single creditI.

>. f you want to automatically create ;*cise invoice during Sales cycle at the time of

billing the tic3 the indicator I/reate ;I?. During depot sales if you do not want to do 8(0ED selection and posting separately

and would li3e to complete 8(0ED selection in one step mar3 the indicator I8(0ED !uto

postI. This will post the selected records into 8(0ED automatically. 4ou cannot cancelthe selection later.

@. f the indicator IDefault (8 qtyI is mar3ed system will default the ;*cise challan

quantity on to the (oods receipt if the ;*cise invoice number is given in the pop9up.C. f the indicator IFolio no createI is mar3ed system will generate Folio numbers for

8(0ED during receipt of e*cise invoice into depot.

W. I!utomatic postingI when tic3ed will post the ;*cise invoice other movementsautomatically along with creation in single step.

O. I/reate #art for loc3 Stoc3I when mar3ed will create a #art during the receipt of

material into loc3ed stoc3 .


42/63

A. I/reate #art for ST'I when mar3ed will create a #art during the receipt of material

through inter plant transfers.

. I/reate #art for consumption stoc3I when mar3ed will create a #art during thereceipt of material into consumption stoc3. ;*cise (roup (overns which set of e*cise

registers a business transaction will be included in.

Following is the relation between e*cise group, plant and registration. 9 n define e*cise

groups in /ustomiGing.Then, in transactions involving e*cise duty, for e*ample, when you post a vendorIs e*cise

invoice, you specify which e*cise group you are using. This information tells the system

which (B7 accounts to post the e*cise to. !t the end of the period, when you come toprepare your e*cise registers, you create different sets for each e*cise group.

ndicates that the plant in question is a depot. 9 Depots are required to prepare register 8(

0ED, and follow different procedures for goods receipt and invoice generation.

9 (8 #er ;*cise nvoice

9 &ultiple (8 for one e*cise invoice , &ultiple credit9 &ultiple (8 for one e*cise invoice , Single /redit

/reate ;*cise nvoice !utomatically 9 nstructs the system to automatically create a Sales

and Distribution $SD% e*cise invoice immediately you create a commercial invoice or apro forma invoice.

The e*cise invoice is created in the bac3ground. 9 f you want to ma3e use of this

function, you must also define thedefault plant, e*cise group, and series groups in /ustomiGing for Sales and Distribution

$SD%, by choosing ;*cise (roup 9 Series (roup Determination.

8(0ED Sales /reation and posting option 9 8(0ED !utomatic 'ption if selected willcreate Depot e*cise invoice by posting the selection of e*cise invoices in single step. fthis is not selected then you need to separately do 8(0ED selection

followed by #( and then 8(0ED verification and posting. f you need automatic

posting of 8(0ED selection then the #ost (oods ssue should have been completedbefore running 8(0ED selection.

Default e*cise qty in (8 9 f this indicator is tic3ed then while doing (oods 8eceipt

using I&AI system will default the e*cise invoice quantity on to the (oods receipt

document.

Folio number for depo #osting 9 f this indicator is mar3ed then while creating ;*ciseinvoice for other movements system automatically does the Verify and #ost. 4ou need not

separately #ost the e*cise invoice

!lso we can set indicator for creation of part for-9 loc3ed stoc3

9 Stoc3 transport order

9 /onsignment stoc3


43/63

&aintain Series (roup 9 n this &( activity, you define the different e*cise series groups

within your company. Series groups allow you to maintain multiple number ranges for

the outgoing e*cise documents. ased on e*cise regulations and e*emptions from theauthorities you can maintain multiple number series for outgoing documents. ut each of

these series has to be declared to the e*cise authorities.

9 Define e*cise series groups based on type of outgoing document

9 !ssign series group to e*cise registration D9 f no financial postings are required for an ;*cise invoice in this seris group then you

tic3 the I2o utiliGationI indicator.

9 f the /;2V!T has to be paid immediately and you need not wait for the Fort nightlypayment then mar3 the Immediate :tiliGationI indicator. ;*ample 9 4ou could define

two series groups, group AA for e*cise invoices, and group AA0 for ?C F> documents.

9 2o account postings for /;2V!T in sales cycle9 2o utiliGation Flag

f you do not need any /;2V!T utiliGation for an e*cise invoice but would li3e to Just

generate an e*cise invoice then you need to mar3 this indicator.f the flag is chec3ed then system will create an ;*cise invoice in the given Series group

but there will not be any account postings or #art0 postings.

mmediate :tiliGation of /;2V!T 9 Specifies that when you create an e*cise invoice, the

system immediately pays the amount from /;2V!T and creates the #art entry. Suchinvoices will not be listed for fortnightly utiliGation.

f you have both fortnightly and immediate utiliGation for the same e*cise group, the

account determination within /2 &( should point to the ;D interim account.

!ccount determination for immediate payment will be done e*actly the same as beingdone for fortnightly utiliGation program.

&aintain ;*cise Duty ndicators 9 n this &( activity, you maintain the e*cise duty

indicators.

&( 7ogistics 9 (eneral Ta* 'n (oods &ovement ndia asic Settings

Determination of ;*cise Duty Select Ta* /alculation #rocedure

n this &( activity, you specify which ta* procedure you want to use for determining

e*cise duties and sales ta*es on input materials in ndia.

9 f you use condition9based e*cise determination, use a copy of the ta* procedure

T!


44/63

&aintain ;*cise Defaults 9 n this &( activity, you define which ta* procedure and

pricing condition types are used in calculating e*cise ta*es using formula9based e*cise

determination.

If you use condition)"ased excise determination, fill out the /#- cond.field and leave all the others "lan;.

If you use formula)"ased excise determination, fill out all of thefields as follows:) &nter the tax rocedure and the ricing conditions that are relevantfor excise tax rocessing.) (ecify the urchasing and sales conditions tyes used for "asicexcise duty, additional excise duty, secial excise duty, and cess.) (ecify the conditions in the sales order that are used for exciserates.) (ecify the countervailing duty condition tye used for imorturchase orders.

Retrn -aterial Fro- csto-er

4ou need to receipt the reJected goods through SD &odule $V!A 9 Sales 'rder type

8;%.

The steps are as follows -

. /reate a return request. $:sing Sales 'rder in SD%

0. /reate outbound delivery according to return request.

E. f the setting is correct in the outbound delivery screen S!# will automatically switch

post goods issue button into post goods receipt. The setting is in sales order item categoryand delivery type.

>. n the standard system the movement type used is @?.

?. !fter post goods issues receipt is done using outbound delivery, the quantity is placed

in bloc3ed stoc3 without value updating.

@. 4ou will then decide if the return quantity are indeed bad stoc3 or not.

C. Transfer #osting from bloc3 stoc3 to unrestricted stoc3 $mvt type >?E%, this will have

accounting effect $Debit nventory, /redit /'(S%

W. (oods ssue to scrap account how to create new titles which can be used in creating the

address view on the Vendor master.YT9/ode-


45/63

What 'rocesses are in6ol6ed with Csto-er Retrns> How do we

create a re'lace-ent order, and what shold we do i" a re'lace-ent is not issed>

! return is a sales document used in complaints processing for when a customer sends

goods bac3.

4ou enter a return in the system if the customer returns damaged goods, or goods that had

been delivered for sale on approval. The return causes the system to- 8egister the receiptof goods using a returns delivery, and post the goods to stoc3 $for e*ample, bloc3ed

stoc3%.

/reate a credit memo, once you have chec3ed the goods and approved the complaint. !

return is another type of sales document li3e a standard order.

The return triggers the following functions-

9 Delivery $returns delivery%9 illing $for creating a credit memo%

1hen you create a return based on a complaint, you- #ost the goods to your warehouse

for chec3ing !nd then, implement one of the following activities-

9 !pprove the complaint and create a credit memo9 !pprove the complaint, and implement a free of charge subsequent delivery based on

the return

9 8eJect the complaint

#( $#ost (oods ssue% may be cancelled by Transaction code V7AO. The accountingdocument is Just the reverse of the original #( document.

n my company, we use proJect stoc3 $movement type @A for #(%. V7AO creates the

movement type @A0 . ut rather than V7AO, the generally accepted method in mycompany for the reverse items is to use the movement type @?E, bac3 to the to the

storage location. The accounting document ta3es the cost from the proJect and moves

it bac3 to the storage location.

The movement types are entered in the schedule lines in customiGing, which are thenassigned to the item categories. However, in this process, no invoice ta3es place. f you

have a delivery related invoice, it should be cancelled beforehand.

f you do not give replacement, the /ustomer !ccount needs to be credited.

#lease do not forget to create a illing document $Formally 8eturn /redit &emo% with

reference to return delivery. t is very important in order to close the cycle. f you do notcreate a return credit memo, your delivery will 3eep appearing in the illing Due list


46/63

and with status eing processed. 1hen you create a return order type 8;, the billing

type is pic3ed up as 8; $8eturn /redit &emo% automatically.

1hen you are creating a replacement, you can create a replacement order, delivery, andbilling. To create the replacement order, you can define an order type by copying from

order type '8. n the copy control, you can define the relevant item categories from 8;to '8. 4ou can ma3e reference &andatory for this order type. The delivery type for this

replacement order type will be 7F and billing type F0.

Csto-er Retrns and Re'lace-ent Orders

What 'rocesses are in6ol6ed with Csto-er Retrns> How do we

create a re'lace-ent order, and what shold we do i" a re'lace-ent is not issed>

! return is a sales document used in complaints processing for when a customer sends

goods bac3.

4ou enter a return in the system if the customer returns damaged goods, or goods that had

been delivered for sale on approval. The return causes the system to- 8egister the receiptof goods using a returns delivery, and post the goods to stoc3 $for e*ample, bloc3ed

stoc3%.

/reate a credit memo, once you have chec3ed the goods and approved the complaint. !

return is another type of sales document li3e a standard order.

The return triggers the following functions-

9 Delivery $returns delivery%9 illing $for creating a credit memo%

1hen you create a return based on a complaint, you- #ost the goods to your warehouse

for chec3ing !nd then, implement one of the following activities-

9 !pprove the complaint and create a credit memo

9 !pprove the complaint, and implement a free of charge subsequent delivery based on

the return

9 8eJect the complaint

#( $#ost (oods ssue% may be cancelled by Transaction code V7AO. The accountingdocument is Just the reverse of the original #( document.

n my company, we use proJect stoc3 $movement type @A for #(%. V7AO creates the

movement type @A0 . ut rather than V7AO, the generally accepted method in mycompany for the reverse items is to use the movement type @?E, bac3 to the to the

storage location. The accounting document ta3es the cost from the proJect and moves

it bac3 to the storage location.


47/63

The movement types are entered in the schedule lines in customiGing, which are then

assigned to the item categories. However, in this process, no invoice ta3es place. f you

have a delivery related invoice, it should be cancelled beforehand.

f you do not give replacement, the /ustomer !ccount needs to be credited.

#lease do not forget to create a illing document $Formally 8eturn /redit &emo% with

reference to return delivery. t is very important in order to close the cycle. f you do not

create a return credit memo, your delivery will 3eep appearing in the illing Due listand with status eing processed. 1hen you create a return order type 8;, the billing

type is pic3ed up as 8; $8eturn /redit &emo% automatically.

'hen you are creating a relacement, you can create a relacement order,delivery, and "illing. To create the relacement order, you can definean order tye "y coying from order tye O%. In the coy control, youcan define the relevant item categories from %& to O%. Bou can ma;ereference Mandatory for this order tye. The delivery tye for this

relacement order tye will "e C1 and "illing tye 14.

Csto-iing Csto-er Hierarch( in #!

How to con"igre and -aintain the #! Csto-er Hierarch(>

!ll the customiGing is in SDB&aster DataBussiness #artnerB/ustomersB/ustomers

hierarchy

% Define hierarchy type- Just put and D and a name to the new hierarchy.

0% Set partner determination- if you want to user the hierarchy in price determination,then, in the orders, at the header level, you have to have a #artner #rocedure with apartner function for each level. n the partner procedure, in each partner function you

must indicate the source partner function. 1ith this informacition, in the order, you

obtain the bussiness partner for each partner function.

E% !ssign acount groups- you indicate which accounts groups are allowed for being part

or your hierarchy.

>% !ssign sales areas- symple you indicate wich sales areas are allowed in your hierarchy.

$Here you can customiGe common sales areas, Just for not having to build de hierarchy in

all the different sales areas%.

?% !ssigning hierarchy type for pricing- you indicate which classes of documentos uses

hierarchy in pricing determination.

t is possible to maintain so called customer hierarchies. This might be useful when fore*ample you create a condition discount for a customer that is part of such a hierarchy

structure. !ll subnodes in the hierarchy below that customer, will thus receive the same

discount.


48/63

/ustomer hierarchy setup, firstly decide the hierarchy type to be used.

The standard is type !.

4ou can also assign a partner function to the customer so that the higher level customer in

the hierarchy is copied into a sales order as a partner function 9 but you donIt need thatrightP

2e*t assign your customer account group to the hierarchy type. !nd enter the

combinations that will be allowed for creating the hierarchy.

4ou want to assign a ship9to to a payer. So enter the ship to account group and enter thepayer account group as the higher level.

4ou must also ma3e an entry for permitted sales area assignments. So if you want to a

hierarchy for customers in the same sales area then enter the sales area and enter the same

one as the higher level sales area.

!ll these settings can be found in the &(. :nder SD 9 master data 9 business partners 9customers 9 customer hierarchy

4ou use for e*ample customer hierarchy when you have an company li3e :nilever and

you agree both on a discount. :nilever does have different locations B businesses and you

have to maintain the discount for all customers. f you use a customer hierarchy you canmaintain the discount for the partner in the top of the hierarchy and in this way it will be

valid for all customers in the hierarchy.

Basic #! estions On Prodct Hierarchies

What is the signi"icance o" 'rodct hierarch(>

!lphanumeric character string for grouping materials by combining various

characteristics. The product hierarchy is used for evaluation and pricing purposes.

! product hierarchy is an alphanumeric character string which consists of W characters atthe most. #roduct hierarchy thus define the product and its composition.

To ta3e an e*ample, a product hierarchy could be AAAAAA0AAAEAAA>AAA?. The first four

characters AAA could indicate that the product is a car. The ne*t four characters couldindicate AAA0 the plant in which the car has been manufactured. The third set ofcharacters could indicate the color of the car. The ne*t set may determine its engine

capacity and so on. Thus, the product hierarchy helps in defining the product

composition.

#roduct hierarchy is defined in tcode vBC@ according to levels.


49/63

Then it is added as a user defined characteristic in tcode ";S.

t is used for sales reporting functionality based on the product hierarchy. t is used for

profitability analysis reporting.

!i""erent -aterial codes can ha6e sa-e 'rodct hierarch( ?assigned to -aterial

-aster in basic data 6iew@0

1hen a sales cycle happen then after billing document a #! $profitability analysis%

document is created in which product hierarchy is populated and used in /'9#!reporting.

*.'lain the se o" 'rodct hierarch( and the ste' b( ste' 'rocedre to de"ine and

se it>

#roduct Hierarchy is used for #rofitability analysis. 4ou can have ma*imum of three

level in S!# for a product.

4ou have to give the product hierarchy in &aterial master Sales9 Sales 'rg 90 view. 4ou

can define the product hierarchy in &( settings from the following path

/ustomiGing is to be made in-

&( 99 7ogistics (eneral 99 &aterial &aster 99 Settings for "ey Fields 99 Data

8elevant to Sales and Distribution 99 Define #roduct Hierarchies 99 &aintain #roduct

Hierarchy

#roduct hierarchies can be created using code 'VSV. ! product hierarchy is assigned tothe material master record. The hierarchy is bro3en down into specific levels, each level

containing its own characteristics.

! product hierarchy is recorded by the sequence of digits within a hierarchy number. The

hierarchy number can have a ma*imum of W digits with a ma*imum number of ninelevels.

Thus by assigning the hierarchy number to the material, one can determine a

classification of the material. This hierarchy can be used in pricing with each level beingused as field in the condition technique.

t5s li3e if you are having category /!8. n that many cars come into picture.

/!8&!8:TS, Swift, Gen, alto.

A A


50/63

Then from above e*ample AA is the hierarchy for S.

So in that hierarchy many cars come, li3e variants and all the things.

n this way you can ta3e e.g. of wood products also.

It shows the next level of the roduct. Dow many levels that roduct arehaving.

How To Con"igre Prodct Hierarch(

Prodct Hierarch(1

#roduct hierarchies are the domain of materials management. ! product hierarchy isassigned to the material master record. This hierarchy is bro3en down into specific levels,

each level containing its own characteristics. ! product hierarchy is recorded by the

sequence of digits within a hierarchy number. This hierarchy number may have ama*imum of W digits with a ma*imum of O levels. The custom #roduct hierarchies can

be maintained in VBC@.

Prodct Hierarch( N-ber o" chars at $arios le6el1

n the standard system, the product hierarchy consists of up to E levels. The first and

second levels have ? digits and the third level has W. The ma*imum number of digits is Wand the ma*imum number of levels is O.

4ou can define hierarchy nodes at the individual levels of the product hierarchy.

The product hierarchy can be structured via DD/ structure #8'DHS. n the standard

system, a product hierarchy can be created with up to three levels. The individual levelscan contain the following number of digits-

)e6el n-ber o" allowed digits1

?

0 ?E W

This can be changed as of 8elease E.A, where it is possible to e*tend the ma*imum

number of levels to O.

f you want to change the standard setting of #8'DHS, e.g. you want to change thenumber of levels, proceed as follows-

. /reate an appropriate domain in the Data Dictionary $type /H!8 with the required

length%.


51/63

0. !ssign these domains to the standard data elements #8'DH, #8'DH0, ..., #8'DHO.

#lease note that you should use these standard data elements.

E. /hange the structure #8'DHS by creating or deleting fields with reference to the data

elements.

/hoose 66#8'DH2 as field name, where n is the position of the field in the structure

#8'DHS.

4ou want to change the structure of the product hierarchy from ?B?BW digits to ?B?B?BE.

#roceed as follows-

/reate the following domains-

6#8'DHE with length ?, category /H!8,

6#8'DH> with length E, category /H!8,

Change strctre PRO!H#1

Structure #8'DHS in the standard system-

Structure Fields Data element /ategory 7ength

#8'DHS 9

#8'DH #8'DH /H!8 ?

#8'DH0 #8'DH0 /H!8 ?

#8'DHE #8'DHE /H!8 W

Changes according to e.a-'le1

Structure Fields Data element /ategory 7ength

#8'DHS 9

#8'DH #8'DH /H!8 ?

#8'DH0 #8'DH0 /H!8 ?

#8'DHE #8'DHE /H!8 ?

66#8'DH> #8'DH> /H!8 E


52/63

#lease ta3e help of !!#;8 in e*tending the levels of #roduct hierarchy.

/onfigure for #roduct hierarchy at -

S#8'9 &(9 7ogistics 9 (eneral9 &aterial &aster9 Settings for "ey Fields9 Data8elevant to Sales and Distribution9 Define #roduct Hierarchies

=-'le-ent the Prodct Allocation Fnctionalit(

We are reired to i-'le-ent 'rodct allocation "nctionalit( in #AP RE

?*nter'rise $ersion@0

We tried to do the elaborate ste's as 'er the i-'le-entation gide bt are not

sccess"l0 Can (o /indl( hel' b( gi6ing the si-'le ste's "or i-'le-entation0

#lease see if the following helps-

/onfiguration 'verviewL !llocation Specific :sage

.!llocation #rocedure $'V6% The product allocation procedure is the parent of theentire allocation process. !ll materials that are to be included in the allocation scheme are

required to have an allocation procedure assigned to it in the material master. n addition,

as of release >.A, it is in the procedure that the method of allocation is defined. The userhas the opportunity to set an indicator to identify their choice of two different methods

$discrete and cumulative allocation% to evaluate the quantities to be considered for

product allocation.

0.!llocation 'bJect $'V06% The allocation obJect is the root level of the allocationprocess where actual data is entered and planned in 7S. The obJect allows the user to

further brea3 down a procedure into smaller parts for future validation of componentscomprising a specific material

E.!llocation Hierarchy &apping $'VE6% #rimarily, this transaction permits theassignment of an allocation procedure to an 7S information structure. Secondly, a

character is assigned to the information structure to permit collective planning. Finally,

the user can assign a step level to the procedure and information structure to sequence theorder in which allocation quantities are chec3ed. This functionality allows the user the

opportunity to chec3 product allocation against several product allocation scenarios,

before the required quantity is confirmed

>.Define /onsumption #eriods $'V?6% The allocation consumption periods functionalityis only valid if the allocation method flag has been set $'V6%. f you have de9selected

the method field, this functionality is not available. The consumption window indicates

the number of past and future periods to be used in the allocation chec3.

?./ontrol #roduct !llocation $'V>6% n order for the allocation process to functionproperly, allocation control records are created primarily to map allocation procedure

steps to their corresponding obJects so that the allocation data records can be located for


53/63

validation. Secondly, validity periods must be established to indicate when the allocation

control records are active. Finally, the user has the option of establishing a conversion

factor per allocation control record to accommodate '& listings of constrainedmaterials

@.!ctivate !llocation for 8equirement /lass $'V6A% n order to turn on allocation in thestandard order processing functionality, the requirements class must have a flag

indicating that allocation is relevant.

C.!ctivate !llocation for Schedule 7ine /ategory $'V6W% n order to turn on allocation

in the standard order processing functionality, the schedule line must have a flag

indicating that allocation is relevant

W./reate #lanning Hierarchy $&/@% n order to adequately establish allocationquantities, the user must initially determine the level at which the allocation is to ta3e

place and the aggregation factor of the allocation quantities. n this step, the levels for the

collective allocation search procedure are also identified.

O.(enerate &as3ing /haracter $'VC6% :pon completion of the level determination forthe planning hierarchy,