AC240_EN_Col92_FV_Part_A4 (第1页)

第 1 页 / 共 603 页

AC240

Contract Accounts Receivable and

Payable

SAP ERP - Financials

Date

Training Center

Instructors

Education Website

Participant Handbook

Course Version: 92

Course Duration: 5 Day(s)

Material Number: 50093138

An SAP course - use it to learn, reference it for work

第 2 页 / 共 603 页

Copyright

Copyright©2009SAPAG.Allrightsreserved.

Nopartofthispublicationmaybereproducedortransmittedinanyformorforanypurpose

withouttheexpresspermissionofSAPAG.Theinformationcontainedhereinmaybechanged

withoutpriornotice.

SomesoftwareproductsmarketedbySAPAGanditsdistributorscontainproprietarysoftware

componentsofothersoftwarevendors.

Trademarks

• Microsoft®,WINDOWS®,NT®,EXCEL®,Word®,PowerPoint®andSQLServer®are

registeredtrademarksofMicrosoftCorporation.

• IBM®,DB2®,OS/2®,DB2/6000®,ParallelSysplex®,MVS/ESA®,RS/6000®,AIX®,

S/390®,AS/400®,OS/390®,andOS/400®areregisteredtrademarksofIBMCorporation.

• ORACLE®isaregisteredtrademarkofORACLECorporation.

• INFORMIX®-OnLineforSAPandINFORMIX®DynamicServerTMareregistered

trademarksofInformixSoftwareIncorporated.

• UNIX®,X/Open®,OSF/1®,andMotif®areregisteredtrademarksoftheOpenGroup.

• Citrix®,theCitrixlogo,ICA®,ProgramNeighborhood®,MetaFrame®,WinFrame®,

VideoFrame®,MultiWin®andotherCitrixproductnamesreferencedhereinaretrademarks

ofCitrixSystems,Inc.

• HTML,DHTML,XML,XHTMLaretrademarksorregisteredtrademarksofW3C®,World

WideWebConsortium,MassachusettsInstituteofTechnology.

• JAVA®isaregisteredtrademarkofSunMicrosystems,Inc.

• JAVASCRIPT®isaregisteredtrademarkofSunMicrosystems,Inc.,usedunderlicensefor

technologyinventedandimplementedbyNetscape.

• SAP,SAPLogo,R/2,RIVA,R/3,SAPArchiveLink,SAPBusinessWorkflow,WebFlow,SAP

EarlyWatch,BAPI,SAPPHIRE,ManagementCockpit,mySAP.comLogoandmySAP.com

aretrademarksorregisteredtrademarksofSAPAGinGermanyandinseveralothercountries

allovertheworld. Allotherproductsmentionedaretrademarksorregisteredtrademarksof

theirrespectivecompanies.

Disclaimer

THESEMATERIALSAREPROVIDEDBYSAPONAN"ASIS"BASIS,ANDSAPEXPRESSLY

DISCLAIMSANYANDALLWARRANTIES,EXPRESSORAPPLIED,INCLUDING

WITHOUTLIMITATIONWARRANTIESOFMERCHANTABILITYANDFITNESSFORA

PARTICULARPURPOSE,WITHRESPECTTOTHESEMATERIALSANDTHESERVICE,

INFORMATION,TEXT,GRAPHICS,LINKS,ORANYOTHERMATERIALSANDPRODUCTS

CONTAINEDHEREIN.INNOEVENTSHALLSAPBELIABLEFORANYDIRECT,

INDIRECT,SPECIAL,INCIDENTAL,CONSEQUENTIAL,ORPUNITIVEDAMAGESOFANY

KINDWHATSOEVER,INCLUDINGWITHOUTLIMITATIONLOSTREVENUESORLOST

PROFITS,WHICHMAYRESULTFROMTHEUSEOFTHESEMATERIALSORINCLUDED

SOFTWARECOMPONENTS.

g200951995045

第 3 页 / 共 603 页

About This Handbook

Thishandbookisintendedtocomplementtheinstructor-ledpresentationofthis

course,andserveasasourceofreference. Itisnotsuitableforself-study.

Typographic Conventions

American English is the standard used in this handbook. The following

typographic conventions are also used.

Type Style Description

Example text Wordsorcharactersthatappearonthescreen. These

includefieldnames,screentitles,pushbuttonsaswell

asmenunames, paths, andoptions.

Alsousedforcross-referencestootherdocumentation

both internal and external.

Example text Emphasizedwords or phrases in bodytext, titlesof

graphics, and tables

EXAMPLETEXT Names of elements in the system. These include

reportnames,programnames,transactioncodes,table

names, andindividualkey wordsof aprogramming

language,whensurroundedbybodytext,forexample

SELECT and INCLUDE.

Example text Screenoutput. Thisincludesfileanddirectorynames

and their paths, messages, names of variables and

parameters, and passages of the source text of a

program.

Example text Exactuserentry. Thesearewordsandcharactersthat

youenterinthesystemexactlyastheyappearinthe

documentation.

<Example text> Variableuserentry. Pointedbracketsindicatethatyou

replacethesewordsandcharacterswithappropriate

entries.

iii

2009 © 2009 SAP AG. All rights reserved.

Type Style Description
Example text Wordsorcharactersthatappearonthescreen. These includefieldnames,screentitles,pushbuttonsaswell asmenunames, paths, andoptions. Alsousedforcross-referencestootherdocumentation both internal and external.
Example text Emphasizedwords or phrases in bodytext, titlesof graphics, and tables
EXAMPLETEXT Names of elements in the system. These include reportnames,programnames,transactioncodes,table names, andindividualkey wordsof aprogramming language,whensurroundedbybodytext,forexample SELECT and INCLUDE.
Example text Screenoutput. Thisincludesfileanddirectorynames and their paths, messages, names of variables and parameters, and passages of the source text of a program.
Example text Exactuserentry. Thesearewordsandcharactersthat youenterinthesystemexactlyastheyappearinthe documentation.
<Example text> Variableuserentry. Pointedbracketsindicatethatyou replacethesewordsandcharacterswithappropriate entries.

第 4 页 / 共 603 页

AboutThisHandbook AC240

Icons in Body Text

The following iconsareused in thishandbook.

Icon Meaning

Formoreinformation,tips,orbackground

Noteorfurtherexplanationofpreviouspoint

Exception or caution

Procedures

Indicatesthattheitemisdisplayedintheinstructor's

presentation.

iv

©2009SAPAG.Allrightsreserved. 2009

Icon Meaning
Formoreinformation,tips,orbackground
Noteorfurtherexplanationofpreviouspoint
Exception or caution
Procedures
Indicatesthattheitemisdisplayedintheinstructor's presentation.

第 5 页 / 共 603 页

Contents

Course Overview..........................................................ix

Course Goals........................................................... ix

Course Objectives ..................................................... ix

Unit 1: Basics...............................................................1

Concept and Special Functions in FI-CA............................2

Event Technology.......................................................6

Parallel Mass Processes in FI-CA..................................10

Master Data Objects in Contract Accounts Receivable and

Payable.............................................................15

Unit 2: Documents....................................................... 41

Life Cycle of Documents.............................................43

Document Structures.................................................50

Posting Documents...................................................59

Integration with General Ledger Accounting ......................77

Integration with the New General Ledger (Segment Reporting) 95

Account Balance Display ...........................................100

Unit 3: Transactions and Account Determination...............111

Structure of Transactions...........................................112

General Ledger Account Determination ..........................118

Tax Determination....................................................126

USA – Tax Jurisdiction Code (Only relevant for US training) ..139

Unit 4: Incoming Payments...........................................145

Processing Incoming and Outgoing Payments ..................146

Payment Lots and Check Lots .....................................149

Clarification Processing.............................................167

Cash Desk/Cash Journal ...........................................183

Unit 5: Payment Run...................................................203

Prerequisites of the Payment Run.................................204

Payment Program....................................................210

Payment Cards.......................................................229

Check Management.................................................242

Unit 6: Returns Processing...........................................251

Configuration of Returns............................................252

v

2009 © 2009 SAP AG. All rights reserved.

第 6 页 / 共 603 页

Contents AC240

Processing Returns..................................................264

Unit 7: Clearing Control...............................................281

Terminology and Definitions........................................282

Configuration of the Clearing Strategy............................287

Unit 8: Dunning and Collections ....................................315

Dunning – Terminology..............................................316

Configuration and Execution of the Dunning Program..........320

Collection Processing ...............................................349

Unit 9: Interest Calculation...........................................363

Calculation of Interest on Items....................................364

Interest Keys and Calculation Rules ..............................367

Processing of Interest Calculation.................................379

Unit 10: Deferral/Installment Plan...................................397

Deferral: Definition and Processing ...............................398

Installment Plan: Definition and Processing......................404

Unit 11: Other Business Transactions.............................421

Account Maintenance ...............................................422

Reversing Documents and Resetting Clearing ..................430

Document Transfer ..................................................438

Doubtful Entry/Individual Value Adjustment......................441

Write-Off...............................................................446

Unit 12: Security Deposits............................................457

Cash and Non-Cash Security Deposits...........................458

Request, Paymentand Settlement of Cash Security Deposits 461

Unit 13: Correspondence .............................................481

Definition and Types.................................................482

Handling and Customizing..........................................488

The Print Workbench................................................496

Unit 14: Further Integration of Contract Accounts Receivable

and Payable in SAP Modules.........................................503

Overview of the Integration of Contract Accounts Receivable and

Payable............................................................504

Financial Customer Care ...........................................507

Cash Management...................................................514

vi

©2009SAPAG.Allrightsreserved. 2009

第 7 页 / 共 603 页

AC240 Contents

Contract Accounts Receivable and Payable and SD

Integration.........................................................518

Credit Management..................................................526

Unit 15: Appendix: Additional Material............................535

Clearing Control – Special Cases .................................536

Funds Management .................................................541

Outbound Interface..................................................551

Business Intelligence................................................557

vii

2009 © 2009 SAP AG. All rights reserved.

第 8 页 / 共 603 页

Contents AC240

viii

©2009SAPAG.Allrightsreserved. 2009

第 9 页 / 共 603 页

Course Overview

Contents:

• Course goals

• Course objectives

• Course content

• Course overview diagram

• Main business scenario

Target Audience

Thiscourseisintendedforthefollowing audiences:

• Project managers responsible for implementing Contract Accounts

Receivable and Payable

• Theprojectteaminchargeofmodelingthebusinessprocesses

• Administratorsresponsibleforoptimizingprocesses

• Consultants preparing for implementation

Course Prerequisites

Required Knowledge

• SAPFIN (SAP ERP Financials)

• Accounting knowledge

Course Goals

This course will prepare you to:

• Understand the conceptional characteristics of the Contract Accounts

Receivableand Payable (FI-CA) component

• Execute the basic business processes

• MakethenecessarysettingsforconfiguringFI-CA

• Obtain a basic overview of how FI-CA is integrated into other SAP

components

Course Objectives

After completingthiscourse, youwillbeable to:

• ModifyFI-CAbusinessprocessestomeetyourindividualneeds

ix

2009 © 2009 SAP AG. All rights reserved.

第 10 页 / 共 603 页

CourseOverview AC240

• Executeand check these businessprocesses

• Describeintegration with other components

x

©2009SAPAG.Allrightsreserved. 2009

第 11 页 / 共 603 页

Unit 1

Basics

Unit Overview

Unit Objectives

After completing thisunit, you will beableto:

• ExplainthegeneralconceptandspecialfunctionsinFI-CA

• Useeventmanagementtointegratecustomer-specificrequirementsintothe

SAP system without modifyingSAPprograms

• Dramatically reduce the runtime for mass runs (such as payment runs or

dunningprocessing) byusingparallelprocesses

• Explain the most important master data objects in Contract Accounts

ReceivableandPayable(FI-CA)andtheircontrollingelements

Unit Contents

Lesson: Concept and Special Functions in FI-CA.............................2

Lesson: Event Technology........................................................6

Lesson: Parallel Mass Processes in FI-CA...................................10

Lesson: Master Data Objects in Contract Accounts Receivable and

Payable............................................................................15

Exercise 1: Maintain Business Partner Master Data ...................33

1

2009 © 2009 SAP AG. All rights reserved.

第 12 页 / 共 603 页

Unit1: Basics AC240

Lesson: Concept and Special Functions in FI-CA

Lesson Overview

Attheconclusionofthislesson, youwillbeabletoexplainthegeneralconcept

and special functions in FI-CA.

Lesson Objectives

After completingthislesson, you will beable to:

• ExplainthegeneralconceptandspecialfunctionsinFI-CA

Business Example

Figure1: AdvantagesofContractAccountsReceivableandPayable

2

©2009SAPAG.Allrightsreserved. 2009

第 13 页 / 共 603 页

AC240 Lesson: Concept and Special Functions in FI-CA

Figure2: ApplicationsforContractAccountsReceivableandPayable

VariousindustrysectorsuseFI-CAasasubledgerduetoitsseamlessintegration

withthegeneralledgerorinvoicing,forexample,aswellaswithWeb-basedself

servicesandcallcentersolutions. Theexchangeofmessagesintheintegration

is based largely on the XML interfaces of the SAP Netweaver Exchange

infrastructure.

Figure 3: SAP ERP Central Component 6.0

3

2009 © 2009 SAP AG. All rights reserved.

第 14 页 / 共 603 页

Unit1: Basics AC240

Most industry solutions within the ERP release are delivered with SAP ERP

Central Component 6.0.

• TheSAP Switch Frameworkisavailablefor activatingindustry solutions

that are delivered asbusiness function sets.

Inaddition,theindustryextensionsaredividedintobusinessfunctionsets,

to which one or more business functions are allocated. You can activate

these business functions.

Youcanactivateonlyonebusinessfunctionforeachinstance. Withinthe

business function sets, you can activate the business functions from the

industryextensionindividually. Atthestartoftheimplementation, select

thebusinessfunctionsetthatcorrespondstoyourindustrysolutionorthat

containsthebusinessfunctionsyourequire,andactivateit.

Whenyouactivateabusinessfunctionset,youinstalltheSAPsystem. You

canthennolongerdeactivatethebusinessfunctionsetoractivateadifferent

one.

Industry business function sets (BFS) comprise a number of business

functions(BF),whichcanbeactivatedseparately.

• EnterpriseextensionscontaingenericSAPERPbusinessfunctions. Youcan

usetheSAP Switch Frameworkto activateallenterpriseextensions. The

enterpriseextensionsareavailableinadditiontotheindustryextensions.

Youcansimultaneouslyactivatemorethanonebusinessfunctionfromthe

enterprise extension for each instance.

Figure4: SAPERP:Extensionswith theSwitchFramework

4

©2009SAPAG.Allrightsreserved. 2009

第 15 页 / 共 603 页

AC240 Lesson: Concept and Special Functions in FI-CA

Lesson Summary

You should now be able to:

• ExplainthegeneralconceptandspecialfunctionsinFI-CA

5

2009 © 2009 SAP AG. All rights reserved.

第 16 页 / 共 603 页

Unit1: Basics AC240

Lesson: Event Technology

Lesson Overview

Attheconclusionofthislesson,youwillbeabletorecognizethedefinitionand

conceptofeventsinContractAccountsReceivableandPayableandunderstand

howtouseinstallation-specificenhancementsinyoursystem.

Lesson Objectives

After completingthislesson, you will beable to:

• Useeventmanagementtointegratecustomer-specificrequirementsintothe

SAPsystem without modifyingSAPprograms

Business Example

Figure 5: Technology: Event Concept (1)

The event concept allows you to include specific source code passages in the

events(definedpointsinaprogram). Thesepassagesarecapsulatedinfunction

modulesandarethereforeexchangeable. Youusedefinedinterfacestoinclude

them in the events.

You maintain events and their function modules in Customizing for Contract

Accounts Receivable and Payable, under Program Enhancements → Define

Customer-Specific Function Modules.

6

©2009SAPAG.Allrightsreserved. 2009

第 17 页 / 共 603 页

AC240 Lesson: Event Technology

TheFKK_FUNC_MODULE_DETERMINEfunctionmodulerunsforeachevent.

Itusesthesequenceinthefollowingtabletodeterminetheeventmodulesstored

in Customizing that have to be processed:

• TFKFBM (sample function module from Contract Accounts Receivable

and Payable)

• TFKFBS(applicationsfromstandardfunctionmodule)

• TFKFBC(installation-specificfunctionmodules)

Thetechnicalnameofthesamplefunctionmoduleisformedfromthetechnical

codeFKK_SAMPLE_andthenameoftheevent. Inthecaseofasamplefunction

moduledefinedatevent0010,thenamewouldbeFKK_SAMPLE_0010.

As well as the events that are available to all industry components, additional

industry-specificeventsalsoexist. Youcanrecognizethesefromtheencryptionof

the application area in the technical name.

Overview of event nomenclature

FromEvent To Event Application

0 9999 Application-independent

R0 R999 Utilities Industry

V0 V999 Insurance

T0 T999 Telecommunications

P0 P999 Public Sector

X0 X999 Partner Developments

Z0 Z999 CustomerDevelopments

S0 S999 SAP Contract Accounts

ReceivableandPayable

7

2009 © 2009 SAP AG. All rights reserved.

FromEvent To Event Application
0 9999 Application-independent
R0 R999 Utilities Industry
V0 V999 Insurance
T0 T999 Telecommunications
P0 P999 Public Sector
X0 X999 Partner Developments
Z0 Z999 CustomerDevelopments
S0 S999 SAP Contract Accounts ReceivableandPayable

第 18 页 / 共 603 页

Unit1: Basics AC240

Figure 6: Technology: Event Concept (2)

EventscanbemanagedusingtransactionFQEVENTS.

Tousetheeventconcept,youmusthavepriorknowledgeoftheprogramandthe

data structure. If you require functions other than those provided as standard,

proceed as follows:

• Analyzethestandardfunctionmodulesfromtheapplication(TFKBS).These

functionmodulesdefinethe requiredinterfaces.

• Copy the function group that groups customer-specificfunction modules

according to business transactions.

• Program and activate the individual enhancements/changes in the

installation-specific function module.

• Enter the installation-specific function module in the TFKFBC table

(Customizing: Program Enhancements).

• Starttheprogramthat callstheenhancedevent.

8

©2009SAPAG.Allrightsreserved. 2009

第 19 页 / 共 603 页

AC240 Lesson: Event Technology

Lesson Summary

You should now be able to:

• Useeventmanagementtointegratecustomer-specificrequirementsintothe

SAP system without modifyingSAPprograms

9

2009 © 2009 SAP AG. All rights reserved.

第 20 页 / 共 603 页

Unit1: Basics AC240

Lesson: Parallel Mass Processes in FI-CA

Lesson Overview

Attheconclusionofthislesson,youwillbeabletooptimizeyourmassprocesses

in FI-CA.

Lesson Objectives

After completingthislesson, you will beable to:

• Dramatically reduce the runtime for mass runs (such as payment runs or

dunningprocessing) byusing parallelprocesses

Business Example

Figure 7: Technology: Mass Processes in FI-CA

Businessprocessessuchaspaymentordunningruns,inwhichlargevolumesof

dataareprocessed,arerealizedinFI-CAbyusingmassactivities. Massactivities

automaticallysplitthedataset(suchasanumberofbusinesspartnersorcontract

accounts)intomultipletechnicaljobsandprocessthematthesametime.

10

©2009SAPAG.Allrightsreserved. 2009

第 21 页 / 共 603 页

AC240 Lesson: Parallel Mass Processes in FI-CA

Figure 8: Technology: Splitting Processes

YoucanusetheFI-CAmassactivitiestosplitthedatatobeprocessedintoseveral

jobs. Thesystemthenprocessesthesejobsinparallel. Formoreinformation,see

SAPNote607797(Jobcontrolformassactivities: FAQ).

Figure9: Technology: ParallelProcessing–IntervalCreation

11

2009 © 2009 SAP AG. All rights reserved.

第 22 页 / 共 603 页

Unit1: Basics AC240

Whenprocessingdata,thesystemautomaticallysplitsthedatasettobeprocessed

into multiple parallel jobs. The specifications for distributing the key for the

parallel objectsaresavedin variants, which youmust updateperiodically. For

example, you can createa variant for business partnersthat splits the business

partnersettobeprocessedinto1,000 equalintervals.

Duringparallelprocessing,thesystemmakessurethattheprocessesdonotblock

eachotherduetochangingaccessestothesamedatabaseresources. Thiscould

be the case, for example, when document numbersareassigned or transaction

figures updated.

Apaymentrunforallbusinesspartnersstartsseveralprocesses(forexample,10)

thathandletheintervalsautomaticallyoneaftertheother. Onceanintervalhas

beenfullyprocessed,thesystemprocessesthenextfreeinterval. Ifallintervals

have been processed, and therefore all technical jobs completed, the business

task also receives the status Completed.

Figure 10: Technology: Parallel Processing – Portioning

12

©2009SAPAG.Allrightsreserved. 2009

第 23 页 / 共 603 页

AC240 Lesson: Parallel Mass Processes in FI-CA

Figure11: Technology: ParallelProcessing: Implementation

For moreinformation about schedulingbatch processesinFI-CAandworking

withtheFI-CAjobcontainer,seetheSAPSupportPortal(keywordFO-JOB).

13

2009 © 2009 SAP AG. All rights reserved.

第 24 页 / 共 603 页

Unit1: Basics AC240

Lesson Summary

You should now be able to:

• Dramatically reduce the runtime for mass runs (such as payment runs or

dunningprocessing) byusing parallelprocesses

14

©2009SAPAG.Allrightsreserved. 2009

第 25 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Lesson: Master Data Objects in Contract Accounts

Receivable and Payable

Lesson Overview

ThislessondescribesthemainfunctionsofmasterdatainFI-CA.

Lesson Objectives

After completingthislesson, youwillbeable to:

• Explain the most important master data objects in Contract Accounts

ReceivableandPayable(FI-CA)andtheircontrollingelements

Business Example

Figure 12: Central Objects

15

2009 © 2009 SAP AG. All rights reserved.

第 26 页 / 共 603 页

Unit1: Basics AC240

Figure 13: Business Partners and Roles: Examples

Application-neutraldata,suchasname,address,bankdetails,andpaymentcards,

is stored in the business partner masterrecord. Special requirements involved

in setting up business partners that are organizations, groups, and individuals

are also fulfilled.

The SAP BusinessPartner also providesan open infrastructure for linking the

application-specificattributesofthebusinesspartner. Fromabusinesspointof

view, thislinkismadebyway of therole concept.

Onthetechnicalside,SAPBusinessPartnerofferspredefinedinterfacesthatcan

beusedtolinkbusinesspartnerattributesfromdifferentapplications.

ThismeansthatexistingbusinesspartnermappingwithintheSAPsystemcanbe

gradually integratedinto SAP BusinessPartner.

16

©2009SAPAG.Allrightsreserved. 2009

第 27 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Figure 14: Business Partner: Role Definition

A business partner role corresponds to a business context in which a business

partnercanappear. Abusinesspartnercanhaveseveralroles,suchasacontract

partner(FI-CA),contactperson,prospect(potentialcustomer),orbusinesspartner

(general).

Theexampleaboveshowsthatbusinesspartnerscanassumeseveralroles(contact

person, contract partner) depending on the business process in which they are

involved.

BP rolesconsist of blocks(attributes) known asdata sets. Theseareshown as

little black boxes in the graphic above.

SAP Business Partner offers an open infrastructure. This means that other

components (ERP core, industry components, components of development

partners, and a customer-specific components) can easily add their own

application-specific business partner data.

AsofERP2005,businesspartnersmustexistinthebusinessroleMKKforrole

category MKK. If youusetime-dependent businesspartnerroles, notethatthe

MKK business role for role categoryMKK cannot have a time limit. It must

alwayshaveavalidityperiodfromtoday'sdatetoDecember31,9999. Youmay

not, and cannot, restrict the validity of thisrole.

17

2009 © 2009 SAP AG. All rights reserved.

第 28 页 / 共 603 页

Unit1: Basics AC240

Figure 15: Business Partner: Business PartnerCategory

AbusinesspartnerinFI-CAusuallyrepresentsthepersonorlegalentityforwhich

youhavetoprocessincomingandoutgoingpayments.

Business partner category is the term used to classify a business partner as a

naturalperson (forexample, aprivateindividual), groupor organization(legal

entity or part ofalegalentity, such asdepartment).

Thebusinesspartnercategorydetermineswhichfieldsareavailablefordataentry.

For example, if you want to create a business partner as an organization, you

mustenterthelegalforminoneofthefields. Foraperson,youhavetoenterthe

first name, last name, gender, and so on.

Whenabusinesspartneriscreated,thebusinesspartnercategorymustbeselected

(required entry).

Assignmentofthebusinesspartnercategoryisstaticandcannotbechangedonce

the business partner has been created.

Itisnotpossibletocreateanyotherbusinesspartnercategories.

18

©2009SAPAG.Allrightsreserved. 2009

第 29 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Figure 16: Business Partner: Business PartnerGroup

A business partner group is a classification of business partners according to

criteria that the user can freely define.

The procedure in Customizing isas follows:

• Definenumber rangesfor thebusinesspartners

• Definegroupingsforthebusinesspartnerandassignnumberranges

Number range intervalsand a type of number assignment are defined for each

number range:

• Typeofnumberassignment: externalorinternalnumberassignment

• Numberrangeintervalsdeterminewhichnumbersarepermitted.

Businesspartner numberrangesapplyto all clients. TheSAPsystem contains

numberrangesforthegroupsprovided,andthesecanbechangedifnecessary.

19

2009 © 2009 SAP AG. All rights reserved.

第 30 页 / 共 603 页

Unit1: Basics AC240

Figure 17: Business Partner: Business Partner Type

Thebusinesspartnertypecontrolsthefieldstatusdefinition(whichfieldsinthe

business partner master record are mandatory, hidden, displayed, or optional)

when creating a business partner in FI-CA.

Youcanusebusinesspartnertypestogroupbusinesspartnersaccordingtoyour

own criteria.

Youcanfindthebusinesspartnertypeinthecontroldataofthebusinesspartner.

Figure 18: Business Partner: Address Management

20

©2009SAPAG.Allrightsreserved. 2009

第 31 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Centraladdressmanagementallowsyoutoassigndifferentaddressestoabusiness

partner for different functions (see Customizing for business partner address

types). Theseaddressescan be classified according to address types(delivery

address, correspondence address, and so on).

Youcanmaintainanynumberofaddressesforeachbusinesspartner,butonlyone

addresscan bespecified asthestandard address.

Mailingdataandinformationaboutdifferentcommunicationtypesisassignedto

theaddress. Youcanmaintain different communicationtypesforeachaddress

(telephone,fax,Internetmailaddress,pagerservices,printers,remotemail,Secure

Store&Forward,telex,teletex, URI/URL/FTP,X.400).

Theaddresscanbeusedindependentlyofthebusinesspartner.

The address isan object in itself andoffersinterfaces. The businesspartner is

basedonthese,andofferscorrespondingbusinesspartnerinterfaces.

ThestandardaddressisalwaysmaintainedontheAddressscreen.

AsofERP2005,thestandardaddressofabusinesspartnerisnolongerspecified

usingindicatorXDFADRintableBUT020. Thisindicatorisobsoleteandyoucan

nolongerselectitonmanualentry. Asof Release6.40, thestandardaddressis

specifiedwiththeaddressusageXXDEFAULT.Ifyouwanttouseaddressesona

timebasis,youcancreatedifferentstandardaddressesfordifferentperiods. For

eachtime,youcanspecifyoneaddressasthestandardaddressforthebusiness

partner.

Figure 19: AddressManagement: AdditionalFunctions

To date, SAP uses UNISERVsoftware to carryout theabovechecks. Paricon

interfaces establishthe link to CentralAddress Management. Integration with

other software providers is also planned.

21

2009 © 2009 SAP AG. All rights reserved.

第 32 页 / 共 603 页

Unit1: Basics AC240

IntegrationisensuredbymeansofBAdIs(BusinessAdd-Ins). BAdIsareopen

interfaces that can be created at every level of a multi-level system landscape

(SAPERP,countryversions,ISsolutions,partner,customer,andsoon).

Examples of checks:

• Addresscheck: Postalcodes,citiesandstreets,andcombinationsofthese,

arecheckedforconsistency. Forinformationaboutactivatingcentraladdress

management, seeSAPNotes098050and132948.

• Missingelementsareaddedduringthecheck. Forexample,ifonlythecity

hasbeenentered,thepostalcodewillthenbeadded.

• Whenyoucreateorchangeabusinesspartner,youareofferedanumberof

phoneticallysimilar,existingpartnersforcomparison. Inthiswayyouavoid

creating the same partner more than once.

Anerrortolerantsearchmeansthatyoucansearchforduplicatebusinesspartner

entries using the F4 search function.

Figure 20: Contract Account: Structure and Function

Before a document can be posted, a contract account must be assigned to a

business partner.

A contract account can represent a receivable type. This is required for open

itemaccountingwithinFI-CA.Acontractaccountisthereforeaunitthatgroups

business partner postings.

22

©2009SAPAG.Allrightsreserved. 2009

第 33 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Thecontractaccountcategorydefinesthefollowingattributes:

• Whetheryoucanassignoneormorebusinesspartnerstoacontractaccount

• Whether you can assign oneor more contracts

• Whetheryoucanmaintainacontractaccountonline

• Thenumberrangethatisallowedforexternalorinternalnumberassignment

• Whether it is a one-time account

• Theeditingscreensordatafieldsthatyoucanusetoeditthecontractaccount

You can use the method BAPI_CTRACCOUNT_EASYCREATE to create a

contract account with sample values.

Figure 21: Contract Account: Company Code Group

Figure22: CompanyCodesinContractAccountsReceivableandPayable

23

2009 © 2009 SAP AG. All rights reserved.

第 34 页 / 共 603 页

Unit1: Basics AC240

The company code group includes all company codesthat canbe used to post

to a contract account. One company code group is assigned to each contract

account. Companycodegroupscanoverlap. Forexample,groupG1canconsist

ofcompanycodes0001,0002,and0003,andgroupG2canconsistofcompany

codes 0001 and 0003.

Using the new event 1010, you can check whether a company code group is

permittedinacontractaccount. Thisenablesyoutopreventcross-countrygroups

(incertaincontractaccounts)frombeingused, forexample.

• Exactlyonepayingcompanycodeisalwaysassignedtoeachcompanycode

groupinCustomizing. Apayingcompanycodeisresponsibleforpayment

transactions. You have to define house banks and payment methods for

payingcompanycodes. Severalcompanycodegroupscanhavethesame

payingcompanycode. Thepayingcompanycodedoesnothavetobeinthe

company code group itself.

Youcanalsospecifythepayingcompanycodeinabusinesspartneritem. In

thiscase,thespecifiedcodeoverridesthepayingcompanycodedetermined

viathecompanycodegroupofthecontractaccount. Ifapayingcompany

codespecifiedinthelineitemisinadifferentcountrytothepayingcompany

codedeterminedviathecontractaccount,youalsohavetospecifyapayment

methodinthelineitem. Inthiscaseyoucannotusethepaymentmethods

fromthecontractaccountssincetheyrefertoadifferentcountry.

• Astandardcompanycodeisallocatedtoeachcontractaccount. Youusethe

standardcompanycodeforallpostingsforwhichnocompanycodecanbe

determinedbyothermeans(forexample,forpaymentsonaccount).

Figure 23: Elements of the Customer Profile

24

©2009SAPAG.Allrightsreserved. 2009

第 35 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Thebusinesspartner'spaymentpatternsarereflectedinhis/hercreditworthiness.

Thedunningprocedureisstoredatcontractaccountlevel.

The payment term determines theduedate and, in certain circumstances, the

cash discount deadline.

The clearing category controls payment allocation and the clearing of credit

notes and receivables.

Theinterestkeyisusedtodetermineindividualconditionsforinterestcalculation.

TheaccountdeterminationIDisusedfordetermininggeneralledgeraccounts.

TheaccountclassisnotusedbySAPprogramsandcan,therefore,beusedfreely.

The tolerance group defines limits for payment differences in the incoming

payment.

Thebusinesspartner'spaymentpatternsarereflectedinhis/hercreditworthiness.

You can override automatic determination of creditworthiness by entering a

percentage-basedweightingandcreditworthinessdatamanually.

Figure 24: Creditworthiness 1

Creditworthiness is stored in the business partner's master data record.

Creditworthinesscanbeupdatedmanuallyorinthedunningrun.

25

2009 © 2009 SAP AG. All rights reserved.

第 36 页 / 共 603 页

Unit1: Basics AC240

You can also enter creditworthiness data manually. This means that

business transactions such as a customer complaint over unjustified returns

(creditworthiness improvement) or “black lists” from external credit

evaluators(worseningcreditworthiness)canalsoinfluenceabusinesspartner's

creditworthiness.

Manualcreditworthinessentriesinfluenceabusinesspartner'screditworthiness

in the same way as entries created by the system. They can contain positive

(worseningcreditworthiness)andnegative(improvedcreditworthiness)values.

They can also be reversed.

Figure 25: Creditworthiness 2

Dynamic calculation of current creditworthiness:

Tableof creditworthinessweighting TFK046A:

1 month – factor 4

2 months – factor 3

Thefollowingformulaisusedforruntimeon2006–04–01:

5creditworthinesspoints(February)*3+15creditworthinesspoints(March)*4

= 75 creditworthiness number

When SAP Credit Management from Financial Supply Chain Management

is activated, the creditworthiness recorded in Contract Accounts Receivable

and Payable is transferred to SAP Credit Management and used to evaluate

the internal creditworthiness stored there. So that internal processes such as

dunningandreturnsprocessingcanreacttotheinternalcreditworthinessofSAP

26

©2009SAPAG.Allrightsreserved. 2009

第 37 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

CreditManagementinContractAccountsReceivableandPayable, theinternal

creditworthiness has to be transferred back to FI-CA. It is visible here in the

creditworthinessdisplayinFI-CAwiththedateofthelastreplication.

Figure 26: Payment Terms

Thepaymenttermcontainsdatafordeterminingtheduedateandcashdiscount

terms.

Thepaymentconditionsofgeneralledgeraccountingarereferenced.

FI-CAsupportsthesingle-levelcashdiscountprocedure.

Youcanstoredifferentrulesfordeterminingtheduedateforcreditandreceivables.

Theduedatecanautomaticallybecorrectedtoaworkingdayinconnectionwith

the factory calendar.

27

2009 © 2009 SAP AG. All rights reserved.

第 38 页 / 共 603 页

Unit1: Basics AC240

Figure 27: Lock Concept

Postingstoacontractaccountcanbepreventedbyacentralpostingblock. This

prevents postings, clearing, reversal, and the cancellation of clearing for the

involved account.

In addition, the open items in this account are not dunned. During online

clearingprocessing,openitemsofblockedcontractaccountsareflaggedwithan

appropriateicon. Itisnotpossibletoactivatetheseitems.

Individualbusinessprocessescanalsobepreventedbylocks. Youcansetthese

locksforallitemsatcontractaccountlevel,oratthelevelofanindividualitem.

Lock reasons can be defined in Customizing.

All locks can be given a time limit. Once this limit has expired, the locks are

deactivated. AsofSAPECC6.0,EnhancementPackage4,youcanenterdefault

valuesforthedurationofprocessinglocksinCustomizing.

You can generate a list of business locks in the SAP application menu under

UtilitiesIndustry→ContractAccountsReceivableandPayable→ForContract

Accounts→EvaluationofBusinessBlocks. Whenyoudothis,youcanselectlock

entriesaccordingtobusinesspartner,contractaccount,lockcategory,processand

lockreason. TheentriesareoutputasareportlistorALVlistandcanbesorted

accordingto businesspartner orcontract account.

You can createprocessing locks with transactionFKLOCK2 (Menu : Periodic

Processing → For Contract Accounts). Using the selection criteriaBusiness

Partner,ContractAccount,Contract,andCompanyCode,youcansetmasslocks

foracombinationofLockCategory,Process,andLockReason. Todeletemass

locks, use transaction FPLKDEL.

28

©2009SAPAG.Allrightsreserved. 2009

第 39 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Figure 28: Locks

Locksforcontractaccount: dunning,posting,invoicing,correspondencedunning,

interestcalculation,incomingpayments,andoutgoingpayments.

Youcansetthelockforalimitedperiodoftime. Multiplelockscanalsobesetfor

individual business transactions.

Hint: Ifyouenteronlyonelockreason, youcanchangeordeleteit. If

you have set several time-dependent locks, use the arrowkey to make

changes. Youcanthenenterthechangesinadialogbox.

If you have set multipletime-restrictedblocks, theLockfield contains

only a tilde (~). In this case you can use the arrow key to display the

other locks.

Toevaluatelocksthathavebeenset,usetransactionFPLKAbychoosingPeriodic

Processing→ForContractAccounts→EvaluationofProcessingLocks.

29

2009 © 2009 SAP AG. All rights reserved.

第 40 页 / 共 603 页

Unit1: Basics AC240

Bank Dataand Payment Card Maintenance

• You can use transaction FPP4 to:

– Create new bank details

(determine anewbank IDforevent1053)

– Change or deleteexisting bank details

– Create new payment cards

(determineanewpaymentIDforevent 1054)

– Changeor delete existingpaymentcard detailsand create customer

contacts

– Print confirmation letters

– Control follow-up actions(such asdunningreversal and reversal of

locks)

– Makefurtherchangestoacontractaccount(event1083)

TransactionFPP4makesitconsiderablyeasiertochangebusinesspartner-related

bankdata. Forexample,theMaintainPaymentDatatransactionenablesyouto

changethebankdetailsofacustomer whowantstopaybydirectdebitinstead

of cash. Theinformation ischanged in theBP master recordand independent

objects at the same time.

Youcanuseaflexiblesetofrulestocontrolfollow-upactionssuchasthereversal

of dunnings.

If you set the Create Bank ID indicator in the client-specific settings in

Customizing,youcandetermineanewbankdetailsIDfortherelevantbusiness

partner at event 1053.

If you set the Create Credit Card ID indicator in the client-specific settingsin

Customizing,youcandetermineanewpaymentcardIDfortherelevantbusiness

partner at event 1054.

Withafunctionmoduleprocessedinevent1083youcanmakefurther changes

to the contract account when you save thedata. In this event, you can change

thePlanningGroupfieldinthecontractaccount ifacustomer wantstopayby

direct debit instead of cash, for example.

30

©2009SAPAG.Allrightsreserved. 2009

第 41 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Figure 29: Bank Data and Payment Card Maintenance

Figure 30: Basic Customizing

When Contract Accounts Receivable and Payable is integrated in an industry

add-on,theindustryinquestionmustbeactivated(applicationarea).

TheoverviewsoftheCustomizingactivitiesinthisunitareonlypartoftheIMG.

Customizing settings for the (central) business partner are located under

“Cross-Application Components”.

31

2009 © 2009 SAP AG. All rights reserved.

第 42 页 / 共 603 页

Unit1: Basics AC240

32

©2009SAPAG.Allrightsreserved. 2009

第 43 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Exercise 1: Maintain Business Partner

Master Data

Exercise Objectives

After completingthisexercise, youwillbeableto:

• Create a business partner

• Maintain data for a contract account

Business Example

Youareresponsibleformaintainingbusinesspartnermasterdatainyourcompany.

Anewbusinesspartnerandthecorrespondingcontractaccounthastobecreated.

Task 1: Create business partners

1. CreatethecustomerwiththelastnameBecker##(##=yourgroupnumber)

asabusinesspartner. Toavoidduplicatesinthesystem,firstmakesurethat

this customer exists in the system.

2. Nowcreateabusinesspartnermasterrecordforthenewcustomerwiththe

lastnameBecker##. EnterthebusinesspartnernumberP-AC240-##. Use

theGPEXgrouping“Externalnumberassignment”.

Hint: If theGPEX keyfield is not displayed, press ALT+F12 to

adjust the local layout.

From themenubar, chooseOptions... andnavigatetotheExpert

tab page.

SelectShowKeysinAll Dropdown Lists.

Save your setting by choosingOK.

OntheAddresstabpage,enterthesearchtermGroup##(##=yourgroup

number).

Createa standardaddress for your country.

OntheIdentificationtabpage, addanypersonaldata.

Continued on next page

33

2009 © 2009 SAP AG. All rights reserved.

第 44 页 / 共 603 页

Unit1: Basics AC240

Task 2: Create Contract Account

1. In the next step, you assign a new contract account to business partner

P-AC240-##sothatyoucanpostdata. CreatecontractaccountP-AC240-##

withaccounttype“01”andaccountname“PrivateAccount”forbusiness

partner P-AC240-##.

UsetheexistingcontractaccountT-CA0210##(##=yourgroupnumber)

of businesspartner T-CA0210##(##=yourgroupnumber) asatemplate

account.

On the Payments/Taxes tab page, delete the payment methods in the

“IncomingPayments/OutgoingPayments”areas.

Acceptalloftheothervaluesthatwerecopiedfromthetemplateaccount.

34

©2009SAPAG.Allrightsreserved. 2009

第 45 页 / 共 603 页

AC240 Lesson: MasterDataObjectsinContractAccountsReceivableandPayable

Solution 1: Maintain Business Partner

Master Data

Task 1: Create business partners

1. CreatethecustomerwiththelastnameBecker##(##=yourgroupnumber)

asabusinesspartner. Toavoidduplicatesinthesystem,firstmakesurethat

this customer exists in the system.

a) Choose:

Accounting→FinancialAccounting→ContractAccountsReceivable

andPayable→MasterData→BusinessPartner→Create(FPP1).

b) In the “Create Business Partner” dialog box, leave the “Person”

selectionunchangedandchoose“Continue”(ENTER).

c) Fromthemenubar,chooseBusinessPartner–Openandthenusethe

inputhelp (F4)to findthenameBecker##.

d) Todoso,choosethe“Partner,general”tabpageintheinputhelp(F4).

Field Name Value

Name1/last name Becker## (## = your group

number)

BP Category 1 (Person)

e) Press ENTER.

No entries are found.

f) Choose “Close”.

g) Closethe “Open business partner”dialog box by choosing “Cancel

(F12)”.

Continued on next page

35

2009 © 2009 SAP AG. All rights reserved.

Field Name Value
Name1/last name Becker## (## = your group number)
BP Category 1 (Person)
返回FICO参考资料列表