AC605_EN_Col92_FV_Part_A4 (第13页)

第 458 页 / 共 483 页

Appendix1: Appendix AC605

ThesystemonlyreadsthoseconditiontypesthathavebeenassignedtoaCO-PA

valuefieldintheCO-PACustomizing. Regardlessofthisvaluefieldassignment,

you must note that only certain condition types in Sales and Distribution can

be transferred to CO-PA. These are:

• Revenuesandsalesdeductions,theG/LaccountofwhichwascreatedinCO

withthecostelementtypes,11=“revenue”or12=“salesdeduction”,

• ConditionsthataredefinedasstatisticalinSD,suchastheconditiontype,

VPRS,whichcontainsthecostsofgoodssold. Statisticalconditionsdonot

leadtoapostingtoaG/Laccount. Inaddition,pleasenotethatonlyactive

conditionsaretransferredtoCO-PA.Inactiveconditionsarenottransferred.

Ifalltheconditionsinanitemareinactive,theorderitemisnottransferred

to CO-PA.

Formake-to-orderproduction(theVBRP-VBELVfieldinthebillingdocumentis

filled),thedatahastobetransferredtoCO-PAusingordersettlement.

Figure 179: SD/CO-PA Interface: Plus/Minus Sign Logic

AllvaluesaretransferredtoCOPAwithapositivesign. Forcreditmemos,billing

typeG2, allsignsarereversed. Only inCO-PAreporting, itisdefined thatthe

sales deductions are subtracted from the gross revenues. The reason for this

procedure isthat the revenues in thedifferent SAP applications have different

+/-signs. TherevenuesintheSDModulearemanagedaspositiveamountsbut

asnegativeamountsintheFI Module. Because revenuescanbetransferred to

CO-PAfrombothsystems, the+/-signshavetobeprocessed. Pleasenotethat

thissolutionrequiresthatconditiontypesthataremanagedasnegativeamountsin

SD,suchas,discounts,areassignedtootherCO-PAvaluefieldsasthepositive

condition types, such as, special revenues.

436

第 459 页 / 共 483 页

AC605 Appendix 1: Appendix

Figure180: FI/CO-PAInterfaceversusSD/CO-PAInterface: Plus/MinusSign

Logic

Figure 181: Project System: New Analyses in CO-PA

Settlementofincomingsalesordersforeachbillingelement.

CopyingtherevenuesandcostsrelatingtoincomingordersintoCO-PAsothatan

expectedresultcanbederivedfromtheordersthatbelongtothecurrentperiod

(taxableunder the indicator “processing type”).

Orderbalance=settledincomingorderstogetherwithconsiderationofrevenues

and of the cost of sales already billed.

437

第 460 页 / 共 483 页

Appendix1: Appendix AC605

Youcanmonitorthehistoryofthevalueofincomingordersbydistinguishing:

• New orders

• Changed orders

• Cancellations

• Change of plans

AnalysispossibleinCO-PAandInformationSystem.

Customizing settings - See the release notes.

Figure182: Howto CompareEstimatedValueswith Actuals?

Theaccrueddiscountistransferredtocosting-basedCO-PAthroughastatistical

condition,Cashdiscount,fromthebillingdocumentatthepointoftimewhenthe

billing document is released to accounting.

ThecashdiscountiscalculatedduringtherunofthepaymentprograminFI.To

transfertheactualcashdiscounttoCO-PA,youhavetwooptions.

Firstly, youcanuseautomaticaccount assignment topost actualcash discount

at a higher level into CO-PA.

Secondly,youcanstarttheprogram“ProfitandLossReadjustment”,SAPF181,in

yourperiodclosingactivitiesasshownabove. Actualcashdiscountwillnowbe

assignedtothecustomerleveltotraceyourtruecustomerprofitability.

Inbothcases,makesurethataccruedcashdiscountsandactualcashdiscountsare

storedintwodifferentvaluefields. Thereportingmustbedesignedaccordingly.

438

第 461 页 / 共 483 页

AC605 Appendix 1: Appendix

Figure183: Top DownDistribution ofSingleValuation Views

Previously,intopdowndistributionforactualdata,thedataforallthevaluation

views from legal valuation and profit center valuation used to be distributed.

Currently, individual valuation viewscan be processed separately within atop

down valuation run.

In cases where you use both valuation views but are only interested in one

valuationviewatanextensivelevel,itisagoodideathatyouperformtopdown

distributionjust for thisview. Thisallows youto reduceruntimesin topdown

distributionandavoidgeneratingunnecessarilylargevolumesofdata.

439

第 462 页 / 共 483 页

Appendix1: Appendix AC605

Figure184: TopDownDistributionofVariousRecord Types

With top down distribution, you can concurrently distribute data from several

record types, in a single run. This eliminates the need to re-enter the same

parametersforseparaterunsforeachindividualrecordtype.

Figure185: SpecifyingtheCurrencyTypeforReferenceData

440

第 463 页 / 共 483 页

AC605 Appendix 1: Appendix

Top down distribution offers you more flexibility in entering reference data.

Insteadofautomaticallyapplyingtherespectivecurrenciesofthereferencedata,

youcannowindicateafixedreferencecurrency–thecompanycodecurrencyor

the operating concern currency.

Figure 186: Reference Data with Various Record Types

Intopdowndistribution,youcanselectdifferentrecordtypesasreferencedata.

Youcanspecifywhetherthereferencedataforthedifferentrecordtypesshouldbe

cumulated or handled separately.

Ifyouchoose“CumulateRecordType”,thereferencedataissummarizedatthe

record type level. This means that the data is processed as if the same record

type applied.

Iftherecordtype isnotcumulated, thenumber of record typesneedsto be the

samefortheactualdataandthereferencedata. Processingobservesthesequence

inwhichtherecordtypesareenteredforthemultipleselection. Inthisway,the

actual data with the first record type is distributed according to the reference

dataof therecord typeoccurring first inthesequence(detailedexamplein the

followinggraphic). (ThisexampleisalsofoundintheF1Helpdocumentation.)

441

第 464 页 / 共 483 页

Appendix1: Appendix AC605

Figure 187: Aggregating Record Types - Example

AdditionalCosting: AggregationwithoutTransactionType

100 = 1000*10/ (10+40+50)

400 = 1000*40/ (10+40+50)

500 = 1000*50/ (10+40+50)

3000

1600 = 2000*80/ (80+20)

400 = 2000*20/ (80+20)

AdditionalCosting: AggregationwithTransactionType

360= 1000*(10+80) / ((10+80)+(40+50+20)+50)

440=1000*(40+50+20)/ ((10+80)+(40+50+20)+50)

200 = 1000*50 / ((10+80)+(40+50+20)+50)

1080 =3000*(10+80) / ((10+80)+(40+50+20)+50)

1320=3000*(40+50+20) /((10+80)+(40+50+20)+50)

600 = 3000*50 / ((10+80)+(40+50+20)+50)

720= 2000*(10+80) / ((10+80)+(40+50+20)+50)

880=2000*(40+50+20) /((10+80)+(40+50+20)+50)

400 = 2000 *50 / ((10+80)+(40+50+20)+50)

442

第 465 页 / 共 483 页

AC605 Appendix 1: Appendix

Figure188: EventPlanningwithObject-DependentRevaluationKey

Events,suchasspecialsalescampaigns,canhaveashort-terminfluenceonthe

sales of products.

In Release 4.5, events in manual and automatic sales and profit planning can

be taken into account.

Fromthefunctionalperspective,aneventcanbeseenasarevaluationkeylinked

to a specific length of time.

Events can influence thedata of anentireplan or be defined with reference to

specifiedcharacteristics, suchasaspecificregion.

Figure 189: Additional Functions

443

第 466 页 / 共 483 页

Appendix1: Appendix AC605

Figure 190: Recommendations on How to Use Excel (1)

WhenyoudefineyourExceltemplate,youshoulddistinguishbetweentwotypes

of Excel sheet in Customizing:

• AnSAPspreadsheet,whichisusedtotransferdataintotheR/3Enterprise.

• FurtherExcelsheetsinwhichtheplannerprocessesthedata.

Macrosareusedtotransferdatabetweenthesheets.

When you plan with the SAP spreadsheet, you should be aware of the special

features:

• YoucannotmakeanyfurtheralterationstothepositionofthedatainExcel

whenplanning. Youcannotdeletecolumnsormovecellsatthisstage.

• YoucanaddnewentriesintheSAPspreadsheetonlyinthelinebelowthe

totals line.

• Todisplaypossibleentries,youcanusethebuttonintheR/3environment

designed for this purpose.

• Allother R/3planningfunctionsrequireyou toselect therequiredlinein

ExcelandtoperformtherequiredfunctionintheR/3menubar.

444

第 467 页 / 共 483 页

AC605 Appendix 1: Appendix

Figure 191: Recommendations on How to Use Excel (2)

Duetotherestrictionsof theSAPsheet, aprocedurecanbefollowedinwhich

dataiscopiedfromtheSAPsheetontoadifferentExcelsheet.

YoucanusealltheExcelfunctionstocreatedata,depictwithgraphicsorcalculate

using models.

After you have finished working on the appropriate record, data istransferred

backintotheSAPsheetusingamacro. Formoreinformation,seetheappropriate

example in the documentation.

Note: Whenyoudevelopthemacro,itisgoodideatotestyoursolution

outsideofR/3CustomizingfirstandthentransferitusingCutandPaste.

445

第 468 页 / 共 483 页

Appendix1: Appendix AC605

Figure 192: Using AttributestoDisplayMoreInformation

In previous releases, it was only possible to determine how the lead column

shouldbedisplayed,suchasthekey,characteristicname,orboth. Currently,you

can use attributes to have further information from the master data tables of

characteristics displayed in the lead column.

Selecting “Settings → Characteristic Display” allows you – as before – to

determine how characteristics are to be displayed in the lead column. The

characteristicnameisdisplayedintheaboveexample.

Ifyouselecttheleadcolumnandchoose“Settings→CharacteristicDisplay→

LeadColumn”,adialogboxappearspromptingyoutoselecttheattributestobe

displayedintheadditional columnsof thereport list. The“City”attributewas

selected in the above example.

Finally, selecting “Extras → Attributes” allows you to display a dialog box

showing all theattributes for a characteristic.

446

第 469 页 / 共 483 页

AC605 Appendix 1: Appendix

Figure 193: The Transport Concept (1)

EachindependentinstallationofR/3isknownasanR/3instance. Normally,there

isa1:1ratiobetweenR/3instancesanddatabaseservers. Inaddition,thereareat

leastthreeinstancesforeachSAPproject,fordevelopment, integrationtesting,

and production activities, respectively.

Each operating entity within an instanceis called a client. There are normally

several clients in any instance, which are used for different tasks, such as

playgrounds,development,unittesting,andbackups. Thewayinwhichtheclients

andinstancesareusedinaprojectisknownasaclientstrategy.

The technical operating level of an instance is known as the data dictionary,

DDIC. Notice that the DDIC contains objects, such as tables, programs, and

dataelements, whichareclient-independent. Thismeanstheypertaintoallthe

clients in an instance.

Certainobjectscontaindata,whichisclient-dependent. Datacanbeclassifiedas

masterdata,configurationdata,andtransactiondata. Themasterdataismeantto

bemaintainedontheusersideofsystem. Theconfigurationdatarepresentsthe

settingsthatdefinethetransactionsforR/3Enterprise.

The transaction data is produced by the transactions in R/3 Enterprise.

TransportingindicatestheSAPprocesstomoveitemsbetweenclientswithinan

instance and among instances.

Withtransporting,items,suchasobjectsanddata,arecollectedintotransportable

bundles which are then processed at the operating system level by a systems

administrator. Normally, theconfigurationdataistransportablebetweenclients

withinoramonginstances. Conversely,themasterdataandtransactiondataare

447

第 470 页 / 共 483 页

Appendix1: Appendix AC605

nottransportableinthisway. DDICobjectsaretransportablebetweeninstances

withtheCTStoolbutthereisnoneedtotransportthemamongclientsbecause

they are client-independent.

Figure 194: The Transport Concept (2)

EachindependentinstallationofR/3isknownasanR/3instance. Normally,there

isa1:1ratiobetweenR/3instancesanddatabaseservers. Noticethatthereareat

leastthreeinstancesforeachSAPproject,fordevelopment, integrationtesting,

and production activities, respectively.

Each operating entity within an instance is called aclient. There are normally

several clients in any instance which are used for different tasks, such as

playgrounds,development,unittesting,andbackups. Thewayinwhichtheclients

andinstancesareusedinaprojectisknownasaclientstrategy.

Thetechnicaloperatinglevelofaninstanceisknownasthedatadictionary,DDIC.

TheDDICcontainsobjects,suchastables,programs,anddataelements,which

areclient-independent. Thismeanstheypertaintoalltheclientsinaninstance.

Certainobjectscontainsdata,whichisclient-dependent. Datacanbeclassifiedas

master data, configurationdata, andtransactiondata. Themasterdataismeant

tobemaintainedontheusersideofsystem. Theconfigurationdatasignifiesthe

settings,whichdefinethetransactionsforR/3Enterprise.

The transaction data is produced by the transactions in R/3 Enterprise.

TransportingindicatestheSAPprocesstomoveitemsbetweentheclientswithin

an instance and among instances.

448

第 471 页 / 共 483 页

AC605 Appendix 1: Appendix

Withtransporting,items,suchasobjectsanddata,arecollectedintotransportable

bundles that are then processed at the operating system level by a systems

administrator. Normally,configurationdataistransportablebetweenclientswithin

oramonginstances. Conversely,themasterdataandthetransactiondataarenot

transportableinthisway. DDICobjectsaretransportablebetweeninstanceswith

theCTStoolbutthereisnoneedtotransportthembetweenclientsbecausethey

are client-independent.

Figure 195: Transports in CO-PA

ThetransportfunctionalityforCO-PAisquiteflexibleandsophisticated,allowing

for anumberofwaystoaccomplishtherequiredgoals.

Option1: MostCO-PACustomizingchangesareautomaticallyincludedinchange

requestswhenthechangemanagementsystemisactiveforaclient. Thechange

requestscanbetransportedwithstandardfunctions. Thisapproachisencouraged

for small configurationchanges, especiallydeletions.

Note: NotallCustomizingsettingscanbetransportedusingthisoption, asnot

allCustomizingsettingscreatechangerequestsautomatically. Apartfromthis,

deletionsofmappingsarerequiredtobetransportedwiththisoption.

Option2: Mostconfigurationwhichtakestheformofentriesinatable(technically

speaking,thatconfigurationwhichismodifiedthroughviewmaintenance)canbe

selectivelyaddedtomanuallytriggeredtransports. Manuallycreatedtransports

aretriggeredthroughanoptionintheTableViewmenu.

Note: Thisoptionisfortransportingselectedentriesinatable,suchasmappingsof

conditiontypes. Again,onlysomeconfigurationcanbetransportedinthismanner.

449

第 472 页 / 共 483 页

Appendix1: Appendix AC605

Option #3: Transportation of CO-PA configuration can be managed en masse

through a special tool which has been developed to simplify this process and

enhancethe chancesof consistency and successin CO-PA development. This

transporttoolcantransportallorsomepiecesofanoperatingconcern.

Notes: This optionis required for transportingcertainpiecesof configuration,

suchastheoperatingconcernstructures,otherclient-independentobjects,anda

few other items (see next page).

Option 4: Copying of certain items, such as reports, forms, line item layouts,

reportlinestructures,andplanninglayouts,fromclienttoclientwithinaninstance

andwithinanoperatingconcern ispossiblewithan importtool, without going

through any CTS procedures at all.

Figure 196: CO-PATransport Tool - Operating Concern

Themethodthatneedstobeusedtoprocessanytransportsgeneratedbythethree

CTS-relevanttransportoptions(recallthatthisexcludestheimporttool)depends

on the location of the receiver.

• If the receiver is a client in a different SAP instance, then the standard

system-to-systemtransportmethodisrequiredtoprocessthetransport(s).

• If the receiver is a client in the same instance, then a client copy

accordingtothetransportrequestneedstobeperformed. Thisignoresany

client-independent objects.

It is recommended that the operating concern and summarization levels be

regeneratedin the target afterthetransport of any configurationchanges. This

ensuresthatallthenecessaryitemsintheDDICareupdatedforthechange.

450

第 473 页 / 共 483 页

AC605 Appendix 1: Appendix

The special transport tool is capable of transporting operating concern

configuration pieces separately or together. The pieces basically fall into the

following categories:

• Client-independentstructuresfordatastructuresandsummarizationlevels

• Client-dependentconfigurationforactualpostingsandplanning

• Derivation andvaluation configurationpieces

• Tableentriesforchecktablesandderivationrules

• Miscellaneous,suchasnumberrangegroupsandplanstructures

Notethatnumber rangegroupsand theirassignmentsaretransportedtorecord

typesusingtheTransportTool. Thenumberrangeintervalsthemselvesneedtobe

transportedseparately. Itisagoodideatousethesamenumberrangeintervalsin

allinstancestoavoidpossibleconflictsasaresultoftransports.

Figure 197: Authorization Concept

TheauthorizationconceptintheR/3systemcanbedescribedbriefly,asfollows:

• SAPdeliverscertainauthorizationobjectswiththestandardsystem. These

authorizationobjectsconsistofupto10fields,eachofwhichrepresentsan

element, whichis to be protected, such as“Operating concern”, “Form”,

and “Activity”.

Authorizations are defined by the system owners against these authorizations

objects. Authorizations contain specific combinations of values that are to be

allowedforthefieldsofanobjectduringatransactionthataccessesthatparticular

object.

451

第 474 页 / 共 483 页

Appendix1: Appendix AC605

Inoneprofileyoucannowgroupdifferentauthorizationsthatareeitherassigned

tousersdirectlyortoprofiles. (Theseprofilescanlikewisebeassignedtousers

or more complex profiles). These frequently represent a collection of all the

authorizationsanindividualneedstoperformthejob.

Ausercanhavemorethanoneassignedprofile. Thismeansthatitispossibleto

defineprofilesasasetofdutiesandthenassigntheprofilestoallpersonsbythe

duties they perform or are responsible for.

Figure 198: Authorization Objects in CO-PA

ProfitabilityAnalysisusesthestandardR/3functionsforauthorizations. Aseries

of predefined authorization objects is contained in the standard system. With

these,youcangenerateauthorizationsandprofilestoprotecttheCustomizingand

task functions in the CO-PA component.

For example, inmostimplementations, most CO-PA userswill berestricted to

enterplandataandexecutereports. Managementaccountantsmaybeallowedto

performcostcenterassessmentsandotherallocationsinCO-PA.Othersupport

employeesmayalsobeauthorizedtocreatelineitemsdirectly,toupdatederivation

rule entriesor thecarry out assignment changes.

To restrict the data level in CO-PA, you need to create custom authorization

objectsagainstparticularcharacteristics,valuefields,andkeyfigures. Thedefault

settings for an Operation Concern outline that all data is unprotected (freely

accessible)onthedatalevel until acustomauthorizationobject iscreated on a

field or a combination of fields.

452

第 475 页 / 共 483 页

AC605 Appendix 1: Appendix

For example, you can create an authorization object to protect information

on individual sales employees (e.g. commissions) or on certain product cost

information. Differentauthorizationobjectsareusedforplanningdataandactual

data. Tocontrolonthesamelevelineach, twoauthorizationobjectsneedtobe

created.

R/3Enterprisedeliversthestandardprofile, K_RKE_ALL,whichcontainsfull

authorizations for all the delivered CO-PA authorization objects. This means

that a user with this profile can performany function in CO-PA, if no custom

authorization objects have been created. If objects have been created, then

authorizationsforthemhavetobecreatedandaddedtothisoranotherassigned

profile.

Figure 199: External Data Transfer to CO-PA

Datacanbeuploadeddirectlyintocosting-basedCO-PAthroughtheexternaldata

uploadfeature. Youmay need todothis if acompany isnot implementingthe

SDmodulebutwantssalesdetailsinCO-PAtotakeadvantageofthemodule's

multidimensional reporting capabilities. It might also be used to load historic

datainCO-PAor toloadthedataforcompanydivisionsthatarenotuponR/3

Enterprise.

Withthisfeature,dataisuploadeddirectlyfromtextfilesontheoperatingsystem

levelintothecosting-basedCO-PAtransactiondatatables. Thefeaturedoesnot

simulatethemanuallineitemcreatefeature. Therecordsinthetextfilemustbeof

aconsistentformat,whereeachfieldisallocatedafixednumberofcharacters,and

whererecordsarenotseparatedbycharactersorcarriagereturns.

453

第 476 页 / 共 483 页

Appendix1: Appendix AC605

If you upload data through the external data interface, you need to define the

structureof thefileto beuploadedand assign the fieldsof that structureto the

fieldsoftheoperatingconcern. Thefieldsaremappedtoeachotherthroughthe

aidofassignmentgroups. Thisallowsdifferentmappingsfordatabeinguploaded

in the same structure.

TheconfigurationdescribedaboveisperformedinCustomizing,buttheupload

itselfisconductedinthetasklevelmenuofCO-PA.Youcanusethefunctionfor

bothactualdataandplanningdata. However,youmusttransfertheseseparately.

Duringtheupload,derivation,valuation,andvalidationoccurjustastheywould

foranyothertransactiontransmittingdataintoCO-PA.

Any records that do not pass the validation checks are written to an error file,

whichcanbecorrected. ThisfilecanthenbeuploadedintotheCO-PAcomponent.

Youcanonlydothisonceforeachfileasthesystemmonitorsthefilesinorderto

avoidduplicates. EachfilecanonlybeuploadedintoCO-PAonetime,becausethe

systemkeepstrackofthefilestoensurethatthedataisnotduplicated. Multiple

filescanbeuploadedintoCO-PAatthesametimeformaximumperformance.

Figure 200: Archiving and Deleting CO-PA Data

ProfitabilityAnalysisusesthestandardR/3 functionstoarchiveand delete. In

SAP,archivingsignifiesthetasktocopythedatafromR/3datatablestoanarchive

file. DeletesignifiestheremovalofdatafromR/3datatables. Asaresult,youcan

archivewithoutdeletionorwith deletion. For thelatter, archivinganddeleting

canbeconfiguredtofunction separatelyor together.

In the Profitability Analysis you can archive/delete the line items for selected

periods (but not for the current period). However, summary records can only

be deleted by the year. Actual data and planned data, as well as data in the

454

第 477 页 / 共 483 页

AC605 Appendix 1: Appendix

costing-basedandaccount-basedProfitabilityAnalysisarearchivedanddeleted

separately. Datarecordscanalsobearchivedanddeletedaccordingtotherecord

type.

Incidentally, there are standard functions in the Implementation Guide to

reorganizeor deletethe other types of dataand other items inCO-PA, such as

frozendata, reportdefinitions,formdefinitions, planninglayouts, andlineitem

layouts. Noticethatdeletingfrozendatadoesnotdeletethetransactiondatainthe

standardtablesbutonlydeletesthestoredfrozendataagainstspecificreports.

Figure 201: SAP Enhancement Concept

TheR/3enhancementtoolisusedtoaddcustomizedfunctionstoSAP'sstandard

businessapplications. Throughenhancements,customerscanimplementtheirown

functionswithouttheneedtomodifythestandardSAPcode. Eachenhancement

has a specific purpose.

Enhancements are beneficial because they provide the exits and entrances at

the appropriate places in R/3 along with the necessary data that may be used,

manipulated,andreturned. Enhancementsalsoisolatecustomfunctionssothey

will not harm SAP transactions nor upgrades.

To use enhancements, custom functions must be programmed into the

enhancements. The enhancements must be assigned to enhancement projects.

Inaddition, eachproject must beactivatedfor all of thefunctionscontainedin

the related enhancements to take effect.

455

第 478 页 / 共 483 页

Appendix1: Appendix AC605

Figure 202: CO-PA Enhancement Overview (1)

With the enhancement, COPA0001, you can program the steps to determine

the characteristic values during derivation. The programmed steps in this

enhancementcanbegivenstepIDsandsortedwiththeotherderivationsteps. For

example, thisenhancement might be used to determine thevalue for a special

user-definedcharacteristic,whichisdeterminedbycomplexlogicnotachievable

through derivation rules.

With the enhancement, COPA0002, you can program the steps to calculate or

retrievethespecialvaluesduringvaluation. Separatecalculationscanbedefined

for the planned and actual data. Calculations are assigned user exit numbers,

whichmustbeplacedinactiveCO-PAvaluationstrategiesforthecalculationsto

occurduringthepostingofdata. Forexample,thisenhancementmightbeused

to zero outthevaluesthatarebeingpassedtoProfitabilityAnalysisfor certain

productsthatshouldnotappearinthestandardsalesandmarketingreports,such

as“dummy”productsforfreight,documentation,andservices.

With the enhancement, COPA0003, you can program the characteristic group

thatshouldbeusedwheneveramanualassignmenttoaprofitabilitysegmentis

required,usingmoreextensivecriteriathanstrictlythetransactioncode(standard

CO-PA configuration). This means the same transaction could require the

specificationofvaluesfordifferentcharacteristicswhendifferentsituationsarise.

Forexample,thisenhancementmightbeusedsothatthecharacteristicgroupis

determinedbytheaccountnumberthatisbeingpostedtosothatproduct-related

accountsmighthavetheproductnumberasarequiredfieldintheprofitsegment

andcustomer-relatedaccountsmight needcustomer.

456

第 479 页 / 共 483 页

AC605 Appendix 1: Appendix

Figure 203: CO-PA Enhancement Overview (2)

With the enhancement, COPA0004, you can program the exchange rate type

that should be used for currency transaction when actual data is processed in

costing-basedCO-PAtosomethingotherthanthetype“M”(thedefault).

For example, this enhancement might be used if translation is required at the

bankbuyingrate,thetype“G”,orthebanksellingrate,thetype“B”,insteadof

the average rate, the type “M”.

The enhancement COPA0005 enables you to change or define characteristic

valuesorvaluesinvaluefieldsontheinterfaceswithotherapplicationsusingthe

informationintheoriginaldocument. Thatisnotpossiblewiththeenhancements

forderivationandevaluation,asthesecanonlyworkwiththeinformationentered

in the CO-PA component.

Forexample,thisenhancementmightbeusedtochangethecharacteristicvalues

being derived for an FI journal entry to CO-PA based on information in the

allocation field or thetext fieldof thedocument.

Withtheenhancement, COPA0006, you canprogram the special functionsfor

processingplanning dataduringthemanual andautomaticplanningprocesses.

Eachfunctionisgivenanexitnumber,whichmustbespecifiedwhenconducting

the tasksto access the required calculations.

For example, this enhancement can be used to perform distributions using a

characteristic-specific distribution key, or to revalue using a time-dependent

revaluationfactor,ortorollforwardplan/actualvariancesintofutureperiods.

With the enhancement, COPA0007, you can program special processing

instructionsforexternallyuploadeddataonly. Thismeansyoucanmodifytheline

itemsbeingtransferredintocosting-basedCO-PAthroughthestandardinterface

with some special coding programmed here.

457

第 480 页 / 共 483 页

Appendix1: Appendix AC605

Figure 204: Recommended Follow-Up Activities

Data Used in the Exercises

Data Data in Training DatainIDESSystem

System

OperatingConcern IDEA IDEA

ControllingArea 1000 1000

CompanyCode 1000 1000

SalesOrganization 1000 1000

DistributionChannel 10 10

Division 00 00

Products P-100, P-101, P-102, P-100,P-101,P-102,P-103

P-103

Customer T-CO05A## T-CO05A##

SalesOrderType TA TA

InternalOrderType 0450 0450

Cost Center 4500 4500

Activity Type EH##

Currency UNI UNI

Business Area 5000 5000

Plan Version 100 5## 100

458

Data	Data in Training System	DatainIDESSystem
OperatingConcern	IDEA	IDEA
ControllingArea	1000	1000
CompanyCode	1000	1000
SalesOrganization	1000	1000
DistributionChannel	10	10
Division	00	00
Products	P-100, P-101, P-102, P-103	P-100,P-101,P-102,P-103
Customer	T-CO05A##	T-CO05A##
SalesOrderType	TA	TA
InternalOrderType	0450	0450
Cost Center	4500	4500
Activity Type	EH##
Currency	UNI	UNI
Business Area	5000	5000
Plan Version	100 5##	100

第 481 页 / 共 483 页

Index

A Cost Accounting, 4

Actual Postings, 15 Cost object, 214

Administrator Workbench, Cost of Sales, 13

379 Cost-of-sales accounting, 5

Application Link Enabling, Costing key, 106

377 Costing sheets, 109

Assignment lines, 106 Currency, 298

Customizing Monitor, 90, 410

B

D

Base condition types, 111

Basic reports, 293 Decision-Support

Basic reports:, 311 Information, 12

Bottom up planning, 233 Derivation rules, 88

Business Application Derivation strategy, 84

Programming Interfaces, Detail list, 317

377 Drill-down reporting, 293,

Business Content, 377 295, 311

C E

Calculation condition types, Exception, 297

111 F

Calculation Type, 110

Form reports, 293

Change report, 313

Form reports:, 311

Characteristic derivation, 83

Frozen data, 397

Characteristic group, 313

Characteristic hierarchy, 314 G

Characteristic Values, 38 Global variables, 321

Characteristics, 38–39 Goal Seek, 243

CO orders, 178

I

CO-OM, 13

InfoObject, 379

CO-PA, 13, 15, 394

InfoSource, 379

CO-PA relevant transaction,

integration, 252

CO-PC, 13 K

Company code, 20, 37

Key figure scheme, 313

Condition type, 110

L

Controlling (CO), 13

Controlling area, 20, 37 Line item, 324

Controlling Profitability Local variable, 321

Analysis (CO-PA), 103

459

第 482 页 / 共 483 页

Index AC605

Logistics Execution System, Profit centers, 19

376 Profitability Analysis, 3, 9,

12, 102, 143, 147

M

Profitability Data, 12

Market Segments, 10

Profitability Management, 3

Material Ledger, 4

Profitability Reporting, 4

N Profitability segment, 83

Net Revenue, 13 Profitability segments, 19

Number Format, 298 R

O ratio scheme, 244

Ratios, 243

Online Analytical Processing,

Realignment, 408

381

Reorganize reports, 313

Online Transaction

Responsibility Reporting, 6

Processing, 381

Operating concern, 20, 37 S

Operational Data Store, 380

sales order management

Overhead Cost Controlling,

transaction, 80

142

Sales Reporting, 6

Overhead Costs Controlling,

SAP Business Workflow, 377

173

Scale Basis, 110

P Schedule Manager, 220

PAtransferstructure,180,215 segment level, 393

Parallel valuation, 219 segment table, 393

Performance Figures, 10 settlement profile, 179

Period accounting, 5 Sort, 298

Period indicator, 107 Statistical Postings, 15

Periodic valuation, 103 Summarization data, 397

Planning layout, 237 Summarization level, 395

Plant, 20, 37 T

Product Cost Controlling

Table lookup, 87

(CO-PC), 105

Top down planning, 233

Product Costing, 104

Transaction Data, 15

Production variances, 142,

V

215

Profit Center, 11 Valuation analysis, 113, 156

Profit Center Accounting, 3 Valuation configuration, 104

Profit Center Accounting Value Fields, 41

(EC-PCA), 11, 15

460

第 483 页 / 共 483 页

Feedback

SAP AG has made every effort in the preparation of this course to ensure the

accuracy and completeness of the materials. If you have any corrections or

suggestionsforimprovement,pleaserecordthemintheappropriateplaceinthe

course evaluation.

461