AC240_EN_Col92_FV_Part_A4 (第13页)

第 583 页 / 共 603 页

AC240 Lesson: Funds Management

The transaction class is determined automatically according to the business

transactionandG/L accountthatareused. Thetransactionclassissavedinthe

document header.

TheFMcategoryisinterpretedinFMtoupdatetheFMvaluetype. Example: A

linewithFMvaluetype(54)isgeneratedforinvoice(B).Forpaidinvoice(B),the

invoice(54)isbrokendowninFMandthepaymentline(57)isgenerated. For

FMcategory"PaymentonAccount",justonepaymentline(57)isgeneratedfor

the template FM account stored in FM.

Figure 360: Fiscal Year Change in FI-CA

The“TransferOpenItemsfromFI-CA”report(RFKKFMCF)carriesforwardthe

amountsfromopendocumentsinFMfromtheprevioustothenewFMfiscalyear

foreachaccountassignment. Thismeansthatthenewfiscalyear changeisnot

carriedoutonadocument-by-documentbasis;instead,itiscarriedoutonatotals

basisforeachaccountassignmentaccordingtocertainfieldsgeneratedwhenthe

amountsarecarried forward tothenewfiscal year.

Therestrictionismadeaccordingtothevaluetypesinvoice,downpayment,and

clarification worklist.

You can execute the report several times and a new carryover document is

generated with each run when you do so.

ActivatingFundsManagementIntegration: Step 1

• ActivatetheFundsManagementfieldsforthedocumenttablesasdescribed

in Customizing (DFKKOP, DFKKOPK).

• Assignthecorrespondingcommitmentitems(financialtransaction30,60,90)

tothecorresponding generalledger accounts.

545

2009 © 2009 SAP AG. All rights reserved.

第 584 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

ActivatingFundsManagement Integration: Step 2

• The following derivation rules must be maintained in transaction

FMDERIVE:

– Derivationforthecommitmentitemwithfinancialtransaction60/2for

thereconciliationaccountsthatareusedintheFI-CAenvironment.

– Derivationforthecommitmentitemwithfinancialtransaction30for

certainmaintransactionsandsubtransactions(forexample,0060/0100

payments on account).

– The Payment indicator must be set for main transactions and

subtransactionsthatrepresentpaymenttransactions.

– Derivationforcommitmentitemwithfinancialtransaction90forbank

accounts and bank clearing accounts.

– Derivation for thecommitment itemwithfinancial transaction 50/3

for the clarification accounts that are used in conjunction with the

clarification process.

– SeeSAPNote686383forfurtherinformation.

Derivation Tool

• Predefined derivation rules

• Derivation steps

Figure 361: Derivation Types

546

©2009SAPAG.Allrightsreserved. 2009

第 585 页 / 共 603 页

AC240 Lesson: Funds Management

Figure 362: Assignment

Figure 363: Define Derivation Rule

547

2009 © 2009 SAP AG. All rights reserved.

第 586 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

Figure 364: Table Access

Figure 365: Derivation of FM Account Assignments

548

©2009SAPAG.Allrightsreserved. 2009

第 587 页 / 共 603 页

AC240 Lesson: Funds Management

Fund Accounting

Figure 366: Fund Accounting in FI-CA

Figure 367: Example Posting in FI-CA

WhenFundsManagementisactive,ContractAccountsReceivableandPayable

splitstheFundsManagementaccountassignmentsintoexpendituresandreceipts.

549

2009 © 2009 SAP AG. All rights reserved.

第 588 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

Lesson Summary

You should now be able to:

• ExplaintheFundsManagementupdatelogicinFI-CA

• DescribehowaccountassignmentisderivedinFundsManagement

• Assignbusinesspartnerstothevendorsandcustomers

• DescribetherelationshipbetweenFundsManagementandFI-CA

550

©2009SAPAG.Allrightsreserved. 2009

第 589 页 / 共 603 页

AC240 Lesson: Outbound Interface

Lesson: Outbound Interface

Lesson Overview

This lesson provides an overview of the outbound interface for postings in

ContractAccountsReceivableandPayableandthespecificsettingsforPS-CD.

Lesson Objectives

After completingthislesson, youwillbeable to:

• ExplaintheoutboundinterfaceforpostingsinContractAccountsReceivable

and Payable

Business Example

Figure 368: Outbound Interface for Postings

With the outbound interface of Contract Accounts Receivable and Payable

(FI-CA),youcanforwardinformationaboutbusinesspartnerpostingstoexternal

systems. This can be particularly important if, for a large number of your

documents,insteadofenteringthemintheSAPsystem,youtransferthemtoone

or more external systems via an interface and these systems are dependent on

information, suchasincomingpayment orreversal, inorderto beableto react

in follow-on processes.

Features:

551

2009 © 2009 SAP AG. All rights reserved.

第 590 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

Theoutboundinterfaceforpostingstothebusinesspartnerisbasedonthecreation

of"trigger"entriesatthetimeofthepostings. Wheneveryourequiredatainan

externalsystem,youcanstartamassrunforthetransfer. Thistransfersthedata

totheexternalsystemusingtriggerrecords(seeSAPmenuPeriodicProcessing

→ Data for Externals → Outbound Interface for Business Partner Postings,

transaction FPOITR). Themassactivity sendsthe datato a central integration

serverusingmessagesofSAPExchangeInfrastructure. Fromtherethedatacan

beforwardedtotherespectivereceivingsystem. Toensurethattherecipientof

the message is determined correctly, each message only receives data for one

receivingsystemandtheIDof thereceivingsystem.

Youcantransferthefollowinginformationtoexternalsystemsusingthisinterface:

• Open items of business partner

• Cleareditemsofbusinesspartnersincelast transfer

• Incoming payments since last transfer

• Information about reopened documents

• Detailed informationabout installment plans

Youcaninfluencewhichinformationistobetransferredtotherespectiveexternal

system by means of Customizing settings at company code level or for each

receiversystem. YouconfigurethesettingsinCustomizingforContractAccounts

ReceivableandPayableunderData Transfer→OutboundInterface. Readthe

documentation for the individual activities.

Note for the industry component Public Sector Contract Accounts Receivable

and Payable:

Using the settings in the Customizing activity Making Settings for Public

Sector-Specific Trigger Filtering, you can filter the data by contract account

category and contract account object type.

552

©2009SAPAG.Allrightsreserved. 2009

第 591 页 / 共 603 页

AC240 Lesson: Outbound Interface

Figure 369: Outbound Interface: Settings

Maintain Settings for Company Code

In this activity, for each company code for the outbound interface of business

partnerpostings,youdefinewhetherandhowpostingsaretransferredtoexternal

systems. You can determine whether open items, cleared items, or payment

informationandpaymentinformationforreopenedlineitemsistobetransferred.

AchangetoCustomizingdoesnothaveadirecteffectonthedataoftheoutbound

interfacesincethedataispreselectedusingtriggertables. ChangestoCustomizing

onlyaffectnewpostings. Therefore,youshouldnotmakechangestoCustomizing

during productive operation.

Maintain Settings for Recipient System

Inthisactivity,foreachexternalreceiversystem,youdefinewhetheropenitems,

cleareditems, paymentinformation,andinformationaboutreopenedlineitems

and installment plans is to be transferred.

If, forexample, you havenot selected thetransferofopenandcleareditemsin

the IMG activity Maintain Settings for Company Code for a company code,

these postings in thiscompany code are not transferred to an external system,

irrespective of what you define for the external systems in this IMG activity.

Dependingonthesetting,foreachposting,thesystemsavescorrespondingtrigger

entries that you transfer to the receiver system in the subsequent transfer with

the mass activity Outbound Interface Business Partner Postings (transaction

FPOITR).

Foreachreceiversystem,youalsodefinethelevelatwhichdocumentsaretobe

transferred. Hereyoucanselectbetweenbusinesspartner,contractaccount,and

contract. Thefunctionofthetransferlevelisdescribedbelowusinganexample

553

2009 © 2009 SAP AG. All rights reserved.

第 592 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

with open items. The prerequisite is that the transfer of open items has been

activatedforthereceiversystem. Thefunctionfortransferringclearedandother

items works the same way.

Inthetransferatbusinesspartnerlevel,whenyoupostanopenitemtoabusiness

partner, the system creates a trigger entry with exactly this business partner

(withoutcontractaccountorcontract). Inthenexttransfer,allexistingopenitems

for this business partner are transferred to the external system. The business

partner postings are not filtered. You should select this option if all data for a

businesspartnerisalwaysrequiredinthereceiversystem.

Inthetransferatcontractaccountlevel,whenyoupostanopenitemtoabusiness

partner, the system creates a trigger entry with this business partner and the

contract account postedto. Inthenexttransfer, all existingopenitemsfor this

businesspartnerwithexactlythiscontractaccountaretransferredtotheexternal

system. Youshouldselectthisoptionifyourequireonlythedataaboutspecific

contract accountsinthereceiver systemor, forexample, if onlythedataabout

specificcontractaccountscanbetransferredduetodataprotection.

Tospecifywhichcontractaccountsaretobetransferredtotheexternalsystem,

forevent3800OutboundInterface: FilterTriggersandDetermineReceiver,you

havetodefineanownimplementationanddeletethetriggersdependentonthe

contract account category, for example.

In Public Sector Contract Accounts Receivable and Payable, you can define

filtering based on the contract account category and the contract object type

withoutimplementingevent3800intheIMGactivityDefineSettingsforPublic

Sector-Specific Trigger Filtering.

Inthetransferatcontractlevel,whenyoupostanopenitemtoabusinesspartner

specifyingacontract,thesystemsavesatriggerentrywiththisbusinesspartner,

thecontractaccountpostedto,andthecontract. Inthenexttransfer,allexisting

openitemsforthisbusinesspartnerwithexactlythiscontractaccountandcontract

aretransferredtotheexternalsystem. Youshouldselectthisoptionifyouonly

require the data for specific contracts in the receiver system or you may only

transferthedataofcertaincontracts,fordataprotectionreasons,forexample.

Youdefinewhichcontractsaretobetransferredtotheexternalsystematevent

3800 OutboundInterface: FilterTriggersandDetermineReceiverbydefining

a customer-specific implementation anddeleting the trigger dependent on the

contract.

You canalso define whether, when the documentsare transferred, theexternal

numbersofthebusinesspartner,contractaccount,orcontractaretobereadand

transferredintheXImessage. Forperformancereasons,youshouldonlysetthe

indicatorifyouneedtheexternalnumbersinthereceiversystemasidentification

characteristics.

DefineSettingsforPublicSector-SpecificTriggerFiltering

554

©2009SAPAG.Allrightsreserved. 2009

第 593 页 / 共 603 页

AC240 Lesson: Outbound Interface

Ifyou selectedthetransferat contract level or contractobjectlevel intheIMG

activityMaintainSettingsforRecipientSystem,youshoulddefinewhichcontract

accountcategoriesandcontractobjecttypesshouldbetransferredtotheexternal

system.

Defineexactlywhichcontractaccountcategoriesandcontractobjectshouldbe

allowedtobetransferred. Ifacontractaccountcategoryorcontractaccountobject

isnotentered,notriggersarecreatedforthemandnodocumentsaretransferred

to the system.

If you want to allow all contract account categories, for example, you can use

the generic value “*”.

If thetransfer iscarried out at contractaccountlevel, youcannot maintainany

settings for the contract object type. In this case, enter the value “*” in the

Contract Object Type field.

Ifthistableiscompletelyempty,thesystemassumesthatnofilteringshouldbe

carried out. Then all documents of all contract account categories or contract

object typesaretransferred to the external system. Onceyou make entries for

one of the systems, you have to define which contract account categories and

contractobjectshouldbetransferredforallothertargetsystems. Ifnoentriesare

madefor asystem, itdoesnot createany triggerentriesandthereforedoesnot

transfer any documents.

To make the filter more specific (for example, to include other fields for the

contract accounts or account objects), create your own implementation for

event 3800 by choosing Outbound Interface: Filter Triggers and Receiver

Determination.

555

2009 © 2009 SAP AG. All rights reserved.

第 594 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

Lesson Summary

You should now be able to:

• ExplaintheoutboundinterfaceforpostingsinContractAccountsReceivable

and Payable

556

©2009SAPAG.Allrightsreserved. 2009

第 595 页 / 共 603 页

AC240 Lesson: Business Intelligence

Lesson: Business Intelligence

Lesson Overview

This lesson provides an overview of data extraction from Contract Accounts

ReceivableandPayableandthedisplayinBusinessIntelligence(BI).

Lesson Objectives

After completingthislesson, youwillbeable to:

• ExplaintheFI-CAContentforBusinessIntelligence

Business Example

Figure 370: Business Information Warehouse (BW)

ForevaluationsinBusinessIntelligence(BI),ContractAccountsReceivableand

Payableprovidesextractorsforopenandcleareditemsaswellasforcollection

items and installment plan items. The extraction programs fill the extraction

structure of the relevant DataSources with data from Contract Accounts

Receivable and Payable.

557

2009 © 2009 SAP AG. All rights reserved.

第 596 页 / 共 603 页

Unit15: Appendix: AdditionalMaterial AC240

Figure371: BW:DataExtraction,Transformation,andPresentation

Figure 372: BW: Business Content FI-CA

For evaluations in Business Intelligence, Contract Accounts Receivable and

Payableprovidesextractorsforopenandcleareditemsaswellasforcollection

items and installment plan items. The extraction programs fill the extraction

structure of the relevant DataSources with data from Contract Accounts

Receivable and Payable.

558

©2009SAPAG.Allrightsreserved. 2009

第 597 页 / 共 603 页

AC240 Lesson: Business Intelligence

Lesson Summary

You should now be able to:

• ExplaintheFI-CAContentforBusinessIntelligence

559

2009 © 2009 SAP AG. All rights reserved.

第 598 页 / 共 603 页

UnitSummary AC240

Unit Summary

You should now be able to:

• Handle special cases in clearing control

• ExplaintheFundsManagementupdatelogicinFI-CA

• DescribehowaccountassignmentisderivedinFundsManagement

• Assignbusinesspartnerstothevendorsandcustomers

• DescribetherelationshipbetweenFundsManagementandFI-CA

• ExplaintheoutboundinterfaceforpostingsinContractAccountsReceivable

and Payable

• ExplaintheFI-CAContentforBusinessIntelligence

560

©2009SAPAG.Allrightsreserved. 2009

第 599 页 / 共 603 页

第 600 页 / 共 603 页

第 601 页 / 共 603 页

AC240 Course Summary

Course Summary

You should now be able to:

• ModifyFI-CAbusinessprocessestomeetyourindividualneeds

• Executeand check these businessprocesses

• Describeintegration with other components

561

2009 © 2009 SAP AG. All rights reserved.

第 602 页 / 共 603 页

CourseSummary AC240

562

©2009SAPAG.Allrightsreserved. 2009

第 603 页 / 共 603 页

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.

563

2009 © 2009 SAP AG. All rights reserved.

返回FICO参考资料列表