LTMC: Master data migration

LTMOM: Transactional data migration

https://blogs.sap.com/2020/01/18/ltmc-s-4-hana-replacing-lsmw/: LTMC Blog
https://blogs.sap.com/2015/08/28/billing-plan-periodic-sap-sd-part1/: SD Billing
Plan
https://blogs.sap.com/2013/12/06/asset-impairment/: Asset Impairment
https://blogs.sap.com/2013/12/13/1099-misc-reporting/ 1099 WT reports
https://blogs.sap.com/2015/10/20/ebs-how-to-interpret-a-bai2-file/ EBS Files
S0015990214: Sap1234!
RPCYERK3_XML: T4A
Intercompany Billing: https://archive.sap.com/discussions/thread/3418988
https://blogs.sap.com/2013/09/26/how-to-improve-the-initial-load-by-row-id-
approach/ Table transfer to HANA
http://www.zarantech.com/blog/whats-new-in-1610-and-1709-release-for-sap-s4hana-
finance/
https://www.sapexpert.co.uk/three-ways-to-generate-a-payment-medium-file-in-sap/
Payment file banking
https://blogs.sap.com/2017/02/22/business-partner-customer-vendor-integration-s4-
hana/ BP/ROLE
https://blogs.sap.com/2018/02/04/has-account-based-copa-evolved-enough-to-be-
recommended-in-s4hana/ COPA
https://www.sap.com/documents/2017/07/26113ac0-c47c-0010-82c7-eda71af511fa.html?
lipi=urn%3Ali%3Apage%3Ad_flagship3_detail_base%3Bmg%2B8sX7zRPCW7tfqcVvOzw%3D%3D--
migration
https://sapbazar.com/articles/item/23-s-4-hana-new-asset-accounting-%E2%80%93-
considering-key-aspects Migration 2
https://blogs.sap.com/2014/01/24/steps-to-trasport-hana-content-from-source-to-
target-system-using-lcm/ Transport movement
https://dokumen.tips/documents/dispute-case-creation-sap.html dispute case
https://blogs.sap.com/2014/09/18/dispute-management-usage-i/ dispute case
https://help.sap.com/viewer/62ee292c419c41a9ab9609d73af0aa37/6.17.17/en-
US/e170b6535fe6b74ce10000000a174cb4.html Intercompany
https://eursap.eu/2020/04/16/blog-sap-group-reporting-s4hana-1909/ Group Reporting

assst manaul entry can be posted from OAMK by allowing asset recon accout for
manual posting
Collection management Business partner is compulsory also activate it
dispute managemene work flow is triggered from 0041.0051

AS-IS: In this we analyse the existing business and the current state,
the way current processes are taking place, is reffered to as AS-IS process.

2. TO-BE: As you are implementing SAP you have a desired state of business you
would like to
improvise certain processes revamp others add a few delete a few other and hence
you have in mind a desired business
state after implementation of SAP this staet is reffered to as TO-BE.

The requirements to reach to TO-BE from AS-IS requires GAP analysis.

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=40075655---MTO and MTS

https://archive.sap.com/discussions/thread/596026

In SD account determination In MTO scenario condition type KOFK is used --(MTO

process involves costing)
In SD account determination In MTS scenario condition type KOFI is used,

MTO is related to Vendor and MTS is related to manufacturer

Make-to-order production is a process in which a product is individually
manufactured for a particular custome
can use sales order or project system
for make to order production using the sales order, all costs and revenues involved
for an order item are held collectively at that item.
A particular rule is used that can be changed manually to transfer costs to
profitability analysis.
Make-to-order production is controlled by the requirements type. The requirements
type
is determined on the basis of the MRP group (MRP1) and the strategy group (MRP3) in
the material master record.
In addition, a plant must be assigned for make-to-order items in the sales order.

Primary and Secondary cost element: Cost elements describe the origin of costs.
Cost elements are defined as either

primary and secondary. Primary cost elements arise through the consumption
ofproduction factors that are sourced externally.
Secondary cost elements arise through the consumption of production factors that
are provided internally

primary cost element must be listed first as gl account in chart of account include
revenue account, secondary cost element
used to be define in controlling need not in FI, used for reporting purpose
The Chart of accounts contains all general ledger (GL) accounts belonging to

An accrual occurs before a payment or receipt. A deferral occurs after a payment or

receipt

Parallel landscape. predictive accounting, Migration activity, transport of copies,

fi standard idocs, enhancement,

Financial Accounting.

Expenses and Revenue accounts in Financial Accountng correspond to Primary Cost and
Revenue Elements respectively.

Secondary Cost Elements are used exclusively in CO to identify internal cost Flows
such as assessments or settlements. They do not have corresponding

General ledger accounts in FI and are defined in CO only.When you create a cost
element, you must assign a cost element category. This

Assignment determines the transactions for which you can use the cost element.You
can create cost elements automatically by making default settings that are used

To specify the cost element, or cost element interval that you wish to create.You
can create cost elements manually in bulk with the help of LSMW or BDC.

Primary Cost Element Categories:

1 - Primary costs / cost-reducing revenues

3 - Accrual / deferral per surcharge

4 - Accrual / deferral per debit = actual

11 - Revenus

12 - Sales Discounts

22 - External Settlement

Secondary Cost Element Categories:

21 - Internal Settlement

31 - Order / Project results analysis

41 - Overhead Rates

42 - Assessment

43 - Internal activity allocation

50 - Project related incoming orders: Sales

51 - Project related incoming orders: Others

52 - Project related incoming orders: Costs

61 - Earned

1- Account based CO-PA

In account based CO-PA, COGS is recorded in CO-PA at the time of billing in SD

along with revenue generated from Invoice document generated here.

2- Costing based CO-PA

In case of Costing based CO-PA, the COGS is directly extracted from the Sales and
distribution module through condition type �VPRS�.

To transfer actual data from FI/MM to costing based CO-PA, we need to do define PA
transfer structure in which we define source cost elements
to target CO-PA value field as shown in figure below,
To transfer actual data from Order or Project to costing based CO-PA, we need to do
define PA transfer

Assessment Cycle in CO-PA (T-Code: KEU1):

If we want to allocate any costs from cost centers like Marketing Cost center to
the any CO-PA characteristic like
product e-g Sedan cars we use assessment cycle to allocates costs. The Assessment
cycle contains number of segments,
which describes the receivers, senders, assessment cost element, CO-PA value field/
PA transfer structure and tracing factors

CK11n is used to calculate the standard cost estimate of the product. teh system
considers the bom structure and valuation strategy and
control mention in the costing variant and calculates teh standard cost of the
material. cost estimate is run or the standard cost is calculated monthly,
quarterely etc. and all the analasys of actual production is based against this
standard estimate.

CK40n is used to update the Prices in the material master. it is done by marking
and releasing the cost estimate which is calcualted.
when marking is done, the system will update the price of the material in the
material master in costing 2 tab in the future price.
when release is done then the system will update the current standard price in teh
costing 2 tab. all the postings will then use the price which is updated.

Remember one thing...all the raw materials(which are purchased) are costed at
moving avg price.
and all the semi finished and finished materials(which are produced inhouse) are
costed at standard price.

To check the pricing results, ck11n is used. ck40n is used for updating the prices
in material master.

withholding tax: Withholding Tax is also called as retention tax. Its requirement
of Government to
deduct or withhold a particular percentage from paying to the vendor and pay such
amount to the Government on behalf of other person.
It�s a kind of Indirect Tax
A customer is authorized to deduct withholding tax for services rendered by the
vendor. ... When the Vendor
submits an Invoice the customer is now required to deduct tax on the Invoice amount
reduced by the advance amount

Asset location--plant wise---aso2---time dependent

dunning shud be for debit balance and no block at master data or line item level

FBZP
All com code:define sending and paying com code, cash discount allowed
paying com code: enter paying com code, minimum amount for incoming and outgoing
paymeny, bills of exchange payment allowed
paying method in country: payment method incoming or outgoing, payment method
classification (check, BOE)
Payment method on com code: payment method,minimum and maximum amount allowed,
bank determination: ranking order, bank account, available amount, value date,
expense/charges
house bank:provides information about the bank through which the company makes
payments to vendor/customers

dispute cases: he dispute maybe at a status where it cannot be moved to "closed" -

check status profile

The dispute could be locked - run the case update program "FDM_PROCESS_BUFFE
You cant close a dispute until is has a zero amount I would suggest you create a
status called resolved -
however it will not close unless a credit has been applied to the invoices in the
dispute to bring it back to zero

There was a customer open item. Incoming payment was less than the billing amount
and thus for the remaining amount dispute case was generated.
Later on, the remaining amount was adjusted by FB05 i.e. clear open items as an
Bank charge and thus was cleared of.

So although now the disputed amount is cleared off, the dispute close has not got
the updated information and it is
not changing its status and saying disputed amount exists.

Strangely this has happened as one- off case. Replication of similar case changes
status to close once item is cleared off.

t might be due to the fact that the dispute case was open when the payment or
clearing was processed.
In that case the dispute case does not close automatically as it is readonly mode.

SAP has delivered a program FDM_PROCESS_BUFFER to clear and close such dispute
cases.

I would suggest running this program for that specific dispute case and see what
the result is like.

Account based copa: COGS is recorded in COPA at the time of billing in SD along
with the revenue generated from invoice document generated here.
Costing based COPA: COGS is directly extracted from the sales and distribution
module through condition type VPRS

FI-SD Integration: VKOA

sales order-- no entry

PGI(goods issue) cost of good sold(obyc GBB KEY)

To inventory account
Billing
Customer acc dr
to sales revenue account (ERL t key in pricing procedure)

payment received
Bank clearing
to customer ac

FI-MM Integration: OBYC

PO- No entry
GR posted
Inventory account (key BSX OBYC)
TO gr/ir account (wrx)
Invoice posted
gr/ir account
to vendor account
payment made to vendor
vendor ac
to bank clearing accountant

PA Transfer structure: you have to map the source the cost element which will carry
the values to copa
value field with this assignment system transfer the values in the cost element, to
value field in COPA
PA Trasfer structure form the link btwn COPA components and other components of CO

Distribution: transfer primary cost from a sender cost center to receiving

controlling objects.
distribution received cud be cost center,wbs,IO

Assessment: transfer primary and secondary cost from a sender cost center to
receiving controlling objects
you can reverse both
Depreciation area: You use depreciation areas to calculate different values in
parallel for
each fixed asset for different purposes
Depreciation key: The depreciation key contains the value settings which are
necessary
for determining depreciation amounts. It represents a combination of calculation
rules

Activity Type: The activity type classifies the activities that are to be performed
within a company by
one or several cost centers, Activity types serve as tracing factors for this cost
allocation

Statistical key figures: Statistical key figures are measurable values that are
applicable to cost centers, profit centers, internal orders, or processes.
An example of a statistical key figure would be the number of employees in the
Transportation cost center who perform activities, such as vehicle maintenance.

You can use statistical key figures as an allocation base (or tracing factor) for
periodic allocations such as distribution or assessment,
and for analysis purposes (such as calculating the rent costs per employee).

Types of testing
1. Unit Testing

2. System Testing

3. System Integration security Testing

4. Performance Testing

5. User Acceptance testing

6. Regression Testing

partner profile: Partner profiles are a prerequisite for data exchange. This
involves defining who can exchange
messages with the SAP system and using which port. The partner profile contains
parameters that define the
electronic interchange of data with a partner via that IDoc interface

FI-HR Integration:
assigning the HR wage types to symbolic accounts and the symbolic accounts to GL
accounts.
Symbolic Accout may be P & L Accout or a Balancesheet account.

Plant Abroad: This function lets you do your tax returns for plants in foreign
countries without having to
create a separate company code for these plants.

Vendor Invoice managment:MIRO is the transaction used for invoice verification .

The vendor invoice which you received will be entered in
this screen based upon the approach PO BASED/ non po based. In most of the cases po
based will be used.Based upon the PO details ,
vendor invoice will be verified after entry in the screen . OCR (Optical character
recognition)

Correspondence can be sent to customer/ vendor in various formats like email, and
fax.
Correspondence is basically letters etc. which is sent from SAP to vendor/ customer
etc.
Correspondence can be created individually or collectively, ad-hoc or via automated
batch job

Dunning Areas: Organizational unit that you use to process the dunning program for
example,
by division, or sales organization

Dunning keys enable you to limit the dunning level for an item

Reconciliation Account: When you post items to a subsidiary ledger, the SAP system
automatically posts the same data to the general ledger at the same time.
Each subsidiary ledger has one or more reconciliation accounts in the general
ledger.
These reconciliation accounts ensure that the balance of G/L accounts is always
zero

Open item mgmt: Items posted to accounts managed on an open item basis are marked
as open or cleared.
The balance of these accounts is always equal to the balance of the open items
Bank clearing account/salary clearing/gr/iraccount

Accumulated Dep: Accumulated depreciation is recorded as an asset account with a

credit balance on a company's balance sheet, also known as a contra account.
The accumulated depreciation account is used to reduce the gross amount of the
fixed asset or group of fixed assets reported.
The accumulated depreciation account is an asset account with a credit balance
(also known as a contra asset account);
this means that it appears on the balance sheet as a reduction from the gross
amount of fixed assets reported
The amount of accumulated depreciation is used to determine a plant asset's book
value (or carrying value)

Difference btwn COPA-PCA

The CO PCA allows you to follow profitabilty at profit center level so it gives you
an organizational view of financial performance.

The CO PA is for profitability analysis at segment level, so it gives you an

analytic view of the financial performance of a product or a segment market.

PCA let you determine profits and losses by profit center using either period
accounting or the cost of sales approach.It also lets you analyze fixed capital
and statistical key fig(no of employee, square meter) by profit center

customizing example

Blueprint example: Identification of critical report not delivered with sap r/3
identification of interface that will be needed.
identification of data conversions, sap scripts,

Travel and exp: You can implement a lot of controls for travel/expense
reimbursement (setting reimbursement limits,
setting limits for flagging review, you can set a 2-person approval if the expense
reaches a certain limit)
There is an audit log for every action (great doing financial audits)
You can easily track the status of each expense report along with e-mail
notifications on the status of each report.

workday software: Workday also does not support on-premises or private cloud HR
software deployments

S4 HANA CO
COSP_BAK and COSS_BAK�have been created to store planned data related
to primary and secondary costs,

Actual data of COEP (WRTTP = �04�) is now stored in ACDOCA

Cost elements are no longer required in SAP S/4HANA Finance because they are
created as
G/L accounts using Transaction FS00 now they are part of the chart of accounts.

New reports such as the trial balance will display all postings (primary and
secondary) by
account.

Activation of Material Ledger is a mandatory requirement with SAP S/4HANA. And

activation
of Actual costing is optional in S/4 HANA.There is no default
Material Ledger Type �0000� anymore.

Cost of goods sold (COGS) postings is captured at the time of the goods issue from
the
warehouse.New functions are available to split the COGS posting to multiple
accounts in
accordance with the relative weight of the assigned cost components

Production order variances can be split to multiple accounts to separate scrap,

price
variances, quantity variances, and so on

COPA did not use a direct alignment to the general ledger accounts
Account Based: Based on accounts and uses account-based valuation approach
Costing Based: Groups costs and revenue into Value Fields.

In COPA, Sales and Cost of Sales are updated in value fields when the billing
document is
posted where as in Financial Accounting, Cost of Sales is posted during the Post
Goods Issue (PGI)
http://www.erpfixers.com/blog/ficopa-reconciliation

Typically in Costing based COPA, the values for key figures like Revenue,
cost of goods sold, variances, overheads etc get stored in value field in CE1

Appendix Ledger:Appendix ledger (extension ledger) is mainly for posting the

adjustment entries (may be for management reporting) and it should have a base
ledger.
While reading from appendix ledger the data is retrieved from its base ledger too.
Unlike non-leading ledger which is for legal reporting appendix ledger can
be used for adjustment postings. But stacking of appendix ledgers are not allowed.
Its data is stored in same ACDOCA table
Extension ledger: https://blogs.sap.com/2018/08/24/extension-ledger-and-foreign-
currency-valuation/

ALTERNET Account:
�the account number from your legacy system or
�the account number from a country chart of accounts if your corporate group uses a
standard chart of accounts.

The alternative account number is only issued in the financial statement if you
explicitly assign it to the relevant items in the financial statement version.

Asset HANA: https://www.linkedin.com/pulse/sap-s4h-new-asset-accounting-summary-

sap-s4hana-financial/

FCV
Ie 100 Rs is the Exchange rate diff that 100 Rs will be UNREALIZED EXCHANGE
LOSS....
Entry will be.
DR Unrealized Exchange Loss Acc
CR Balance Sheet adjustment Acc

After Drawing report Well reverse the entry.... Becaus the real transaction lot yet
done...

Reversal entry
DR Balance Sheet adjustment Acc
CR Unrealized Exchange Loss Acc

Realized Exchange Gain/Loss:

ex: We Paid money to vendor against invoice...

Exchange rate is 58 rs
200 Rs is Profit for Company.

Entry will be.

DR Vendor
CR Bank Clearing Acc
CR Realized Exchange Gain

FI12_HBANK: HOUSE BANK

Fiori app: bank account + bank id