...
Data Handling | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| This parameter is used in the two scenarios.
| |||||||||
Take unconfirmed Idocs not older than: | When RESEND is started, Connector will look for all unconfirmed IDOCS not older than defined number of days. The default value is ‘30’ days. | |||||||||
Send Items to FSM on Sales prices update | When the price calculation is performed using the transaction VKPB (Run new price calculation), then the materials involved in this calculation will be sent to the Cloud as a side effect. Once the material data is sent to the Cloud, the price of the material is sent as well. So, if the execution of the VKPB changes the material price, the updated price will be sent to the Cloud as well.
| |||||||||
Select HASH algorithm | Definition of HASH algorithm to be used for HASH-comparison. | |||||||||
| Allow transfer of employees (personnel numbers) who are not supposed to be FSM users (i.e. are not added in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601665). Such employees are sent only as employee records, visible in FSM master data. No account-level user is created for them (therefore licence is not consumed).
Automatic transfer of non-FSM-user employees when added as responsible person of service calls This option triggers automatic transfer of the employee (personnel number) used as responsible of a service call - if it hasn’t been sent before. Example use case: a service order has a responsible person assigned to it (a personnel number). This person has nothing to do with FSM and should not be able to log in/consume licence. However their name/surname must still be visible in FSM on service call level. They cannot be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601665 because this would create an account-level user and consume another licence. If this checkbox is activated, personnel numbers used by service orders (and not added to the user maintainance transaction) will be automatically transferred to FSM and exist as employee master data (with no corresponding FSM user). Manual transfer of non-FSM-user employee If the hereby described option is enabled, transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138800 displays an additional checkbox - ‘Send HR persons to FSM’. When activated, employees not added as FSM-relevant users will also be transferred to FSM. This double-check is necessary to avoid transfer of too many objects. | |||||||||
Do not lock events | During processing of the service order event, a lock with the order number can be set in a subsidiary table. If the lock is set and the next event for the same order is triggered, then the second one waits until the first one is processed. When this option is enabled the system lock is not set for the processed document. By default, during processing of the service order event, a system lock is set so if there are following events related to the same document they must wait for the first one to get processed. This way Connector can ensure the right order of objects’ processing. However it can happen that multiple events are raised for some document and the order in which they are processed is not important and locking mechanism significantly increases the processing time. In such cases, enabling this flag can improve overall performance.
| |||||||||
Do not prefix user’s Id with 'U/' | Due to various historical reasons, user IDs for FSM users based on SAP user names were initially always prefixed with ‘U/’ - similarly to how user IDs for FSM users based on HR personal numbers are prefixed with ‘X/’. However, during a certain period, the user’s ID was also used as the FSM login name, making the ‘U/’ prefix inconvenient. As a result, a feature flag was implemented to allow disabling the ‘U/’ prefix (while IDs for FSM users based on HR records still retain the ‘X/’ prefix). However, since the user’s ID and ‘FSM login name’ became separate properties, this flag has become essentially irrelevant - the ‘FSM login name’ is now always sent without any prefix.
| |||||||||
Use FSM technicians for the docs posting | If switched on the SAP user of the cloud user is used to post changes in SAP whenever technical possible. Otherwise the technical user executing the IDOCs is used for postings and will appear in change documents. Please note that in case where the users are created just with Personal number without ERPUSER marking this option will lead to an error in processing idocs such as "No user found". | |||||||||
| When this feature is enabled, time breaks will not be included in the overall duration of time effort or work time during split calculation. By default, breaks are included in work duration during split calculation. This may result in ‘extra' hours being reported not because a technician worked more but because they took a break in the meantime. This settings allows to reduce impact of breaks on calculated labour costs.
| |||||||||
FieldNameCOBL ConfNo | A field in COBL Structure (an append field or a standard field) which can be used when the service order confirmation is created. It allows the costs analysis to be related to the operations of the service orders. It is used also by the Confirmation Cockpit – the link between the CO document and the operation of the service order. | |||||||||
Use HR trip/travel expense post | Necessary for expenses to be properly posted to travels when using E4C activities (based on customizing in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953879 ).
| |||||||||
Business Partner functionality enabled | This property enable the use of Business Partners (BP Model) functionality by Connector. It is enabled by default in the S/4HANA systems. This flag must be enabled always when partners in SAP system are maintained using the BP transaction.
| |||||||||
Send activities with Service Order | Enabling this feature will result in each change in the service order, triggering the sending of all activities linked with the given order (even those not relevant from the perspective of the activities).
|
...