Configuring Confirmation Posting Date Using the POSTING_DATE Filter

Context

Use the following procedure if you're configuring the confirmation posting date using the POSTING_DATE filter.

Procedure

  1. On the ConfigPanel Home page, select OData Mobile Data Object Configuration. Make sure to select your desired mobile application in the Mobile Application Filter field at the top of the page.
  2. Click on Start of the navigation pathoData Channel Integration Settings Next navigation step oData Mobile Data Object ConfigurationEnd of the navigation path.
  3. In the OData Mobile Data Object List select SAM2210_PM_CONFIRMATION, and then the Data Filter tab.
  4. Expand the Defined Filters list as follows: Start of the navigation pathOperation - CREATE Next navigation step Standard Filter Next navigation step POSTING_DATEEnd of the navigation path. Click the Change button.
  5. Select the existing rule. Ensure the <Low Value> field is set to 1 and is enabled:

    • Default: 1 - Date from Mobile Device without conversion

    • 2 - User Time Zone Date (at the time of BAPI execution)

    • 3 - System Time Zone Date (at the time of BAPI execution)

    ConfigPanel - OMDO Configuration - Data Filter Tab - POSTING_DATE Rule

  6. Save your changes.
  7. Return to the Home page. Navigate to Start of the navigation pathMobile Application Configuration Next navigation step Parameters tabEnd of the navigation path. In the left column, Defined Mobile Applications, select your application.

    The Parameter List populates with a list of all parameters available for the application.

  8. Click the Change button.
  9. Find and highlight the PostingDateFromUserOverride parameter, located in the PMCONFIRMATION parameter group. Set the parameter to one of the following:

    • N: (Default). If set to N, the confirmation posting date is automatically taken from the time zone set on the mobile client.

    • Y: If set to Y, the mobile client user can manually enter a date on the Confirmation screen in the app.

  10. Check the <Active> flag to ensure that the parameter is used by the mobile application. If desired, and if not already checked, check the <No Runtime Change> box to ensure that the value of the parameter isn't overridden at runtime through synchronization processing.
  11. Save your changes.