General purpose | Specify whether expenses reported in SAP FSM should be posted to controlling (KB21N), finance (FB01) or travel/trip. Specify further posting properties, such as activity type or cost element. | ||||
|---|---|---|---|---|---|
Sending transaction (?) | https:/PACG/ECM_EXPENSESND - Expense Type/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38174934
| ||||
Object assignment (?) | Object EXPENSE must be added to https:/PACG/ECM_NOAS - No Object Assignment/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company |
Table of contents
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Expense type definition
Posting to | Finance (FB01), Controlling (KB21N, KB15N) or Travel/Trip.
| ||
|---|---|---|---|
Do not send | Expense type is only defined in FSM Cloud Connector and not sent to the cloud. | ||
ExpenseType | Relevant for posting to trips. Learn more: Expense posting to trips |
CO Expense type settings
Maintain whenever posting to controlling area is set. For amount-based posting (manual cost allocation, KB15N), make sure to enter a cost element. For quantity-based posting (Direct Activity Allocation, KB21N), enter an activity type instead, enable option “Qty. Exp.on” and create a special UDF used for storing expense quantity. The name of the UDF must be entered in /PACG/ECM_VPTYP2 – Define UDF for payment type https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953856 and added to the relevant screen configuration in FSM. You could set a generic quantity in the field ‘Activity quantity’, in case no quantity came from FSM. Activity unit for quantity-based postings should be entered in field ‘ActivityUn’.
| Obsolete. | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ActType | Enter activity type for quantity-based postings (KB21N). If filled, keep the cost element field empty. | ||||||||||||||||
Cost element | Enter a cost element for amount-based postings (KB15N). The cost element will be visible in cost overview in service orders.
| ||||||||||||||||
Cost center det | Specify how cost center for cost documents should be determined.
 Based on WC and Planning Plant, the Cost Center can be determined from IR02: 
| ||||||||||||||||
Cost Center | Enter a cost center to be used for all expenses of a given type in a given company. This has priority over field “Cost center det.” | ||||||||||||||||
Activity quantity / ActivityUn | Enter activity unit when posting quantity-based documents (KB21N). If activity quantity is not entered here, it must be entered in a special quantity UDF. Create it in https:/PACG/ECM_UDF_CONF - UDF Configuration/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138034, add in this transaction as quantity UDF /PACG/ECM_VPTYP2 – Define UDF for payment type https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953856, send to FSM and put it on the expense screen. | ||||||||||||||||
Qty. Exp. on | Necessary when posting quantity-based documents (KB21N), instead of amount-based. See also fields “ActType”, “Activity quantity”, “ActivityUn”. | ||||||||||||||||
As confirmation | Post expense as order time confirmation IW41 (needs settings in /PACG/ECM_VEXPNS and settings for work center in transaction /PACG/ECM_CTET). Requires quantity in field “Activity quantity” or in a special quantity UDF. | ||||||||||||||||
Operation Level | The cost allocation will have reference to operation. | ||||||||||||||||
Data entry profile / Wage type / CATS receiver / Receiver order / CATS amount / Currency | All of these fields are relevant when expenses are posted to CATS. |
FI expense type settings
Maintain whenever posting to finances is set.
FI Document Item settings
Chargeable/nonchargeable
Rules per Service order type can be defined if chargeable or chargeable expenses are allowed. If no setting is made, both possibilities can be used.
C – Only chargeable
N – Only non-chargeable
blank – Chargeable and non-chargeable
S4 SO Chargeable/nonchargeable
| Status | ||
|---|---|---|
|
Rules per SAP S4/HANA Service Order (Lean Order) type can be defined if chargeable or chargeable expenses are allowed. If no setting is made, both possibilities can be used.
C – Only chargeable
N – Only non-chargeable
blank – Chargeable and non-chargeable
Maintain payment types
Defines possible Payment Types for UDF Payment Type – cross-company setting.