ReadSoft Supplier Portal · application server; for example, a war file for Apache Tomcat. Some of...

ReadSoft Supplier Portal Installation and Configuration Guide Version: 3.2 Written by: Product Knowledge, R&D Date: December 2017

© 2017 Kofax. All rights reserved.

Kofax is a trademark of Kofax, Inc., registered in the U.S. and/or other countries. All other trademarks are the property of their respective owners. No part of this publication may be reproduced, stored, or transmitted in any form without the prior written permission of Kofax.

Table of Contents About this guide .......................................................................................................................................... 6

Basic architecture ....................................................................................................................................... 6

Cloud deployment overview ...................................................................................................................... 7

Tasks ......................................................................................................................................................... 7

Simplified cloud deployment steps ............................................................................................................ 8

SAML SSO integration with the Supplier Portal ...................................................................................... 10 Customer effort .................................................................................................................................... 10

Certified Identity Providers (IdP) .......................................................................................................... 10

SAML SSO configuration ..................................................................................................................... 10 SAML SSO terminology ....................................................................................................................... 10

Supported SSO/SLO scenarios ........................................................................................................... 10

Log out ................................................................................................................................................. 13

Unsolicited logout request ................................................................................................................... 13

User information ................................................................................................................................... 14 Security ................................................................................................................................................ 15

Install the Synchronizer ............................................................................................................................ 16

General concepts .................................................................................................................................... 16

Pre-installation ......................................................................................................................................... 16

Installation................................................................................................................................................ 16 Resolution ............................................................................................................................................ 16

Post installation ....................................................................................................................................... 17

Indexing ................................................................................................................................................... 17

Install certificates ..................................................................................................................................... 17 Install in STRUST ................................................................................................................................ 18

Configure the Synchronizer ..................................................................................................................... 19

Basic settings .......................................................................................................................................... 19 Define connection ................................................................................................................................ 19

Define IV settings ................................................................................................................................. 21

Define PO settings ............................................................................................................................... 21

Define MA settings ............................................................................................................................... 21

Define MC settings ............................................................................................................................... 21 Define upload ....................................................................................................................................... 23

Advanced settings ................................................................................................................................... 24

Manage customizing ................................................................................................................................ 24 Initial consistency check ...................................................................................................................... 24

Edit synchronization markers ............................................................................................................... 24 Edit error queue ................................................................................................................................... 24

Run the Synchronizer in SAP .................................................................................................................. 25

Destination ............................................................................................................................................... 26

Selection .................................................................................................................................................. 27

Synchronization ....................................................................................................................................... 28 Initial synchronization........................................................................................................................... 29 Incremental synchronization ................................................................................................................ 30

Check data consistency ........................................................................................................................... 30 Field selection ...................................................................................................................................... 30

Data check ........................................................................................................................................... 32

Logging .................................................................................................................................................... 32

Debugging ............................................................................................................................................... 33 Release information ................................................................................................................................. 33

Synchronize search helps ........................................................................................................................ 34

Parameters .............................................................................................................................................. 34 Destination ........................................................................................................................................... 34

Selection .............................................................................................................................................. 34

Logging ................................................................................................................................................ 34 Debugging ............................................................................................................................................ 34

Synchronize dynamic discounting settings ........................................................................................... 35

Parameters .............................................................................................................................................. 35 Destination ........................................................................................................................................... 35

Logging ................................................................................................................................................ 35 Debugging ............................................................................................................................................ 35

Background jobs ....................................................................................................................................... 35

Configure the Supplier Portal .................................................................................................................. 36

Logon page info text ................................................................................................................................ 36 Information pages ................................................................................................................................ 37

Terms of service ...................................................................................................................................... 38 Company codes ....................................................................................................................................... 38

Email templates ....................................................................................................................................... 39 List of email templates ......................................................................................................................... 40

Placeholders ........................................................................................................................................ 41

System id white list .................................................................................................................................. 42

Portal settings .......................................................................................................................................... 43 Email settings ....................................................................................................................................... 43

General ................................................................................................................................................ 43

Password settings ................................................................................................................................ 45

Self registration settings....................................................................................................................... 46

User handling setting ........................................................................................................................... 47

SAML settings ......................................................................................................................................... 48 SAML SSO setup and IdP configuration.............................................................................................. 48

SAML SSO Service Provider configuration ......................................................................................... 49

Workflow configuration ............................................................................................................................ 50 Workflow step configuration ................................................................................................................. 50

Workflow recipient groups ................................................................................................................... 50

Workflow notification configuration ...................................................................................................... 50

Groups maintenance ............................................................................................................................... 51 Add groups ........................................................................................................................................... 51

Maintain groups ................................................................................................................................... 51

Copy groups ......................................................................................................................................... 51

Delete groups ....................................................................................................................................... 51

Data model ................................................................................................................................................. 52

PROCESS DIRECTOR Accounts Payable ............................................................................................. 52

Incoming invoice ...................................................................................................................................... 63

Purchase order ........................................................................................................................................ 69

Inner document - PO flip .......................................................................................................................... 80

Vendor master data ................................................................................................................................. 81

Supplier Portal 3.2 Installation and Configuration Guide

6

About this guide This document contains the following chapters:

• Basic architecture

• Cloud deployment overview

• Install the Synchronizer

• Configure the Synchronizer

• Run the Synchronizer in SAP

• Synchronize search helps

• Synchronize dynamic discount settings

• Background jobs

• Configure the Supplier Portal

• Data model

Basic architecture The overall architecture consists of the following components:

1. Web Application

The Web Application comprises several components packed together as a deployable file for a target application server; for example, a war file for Apache Tomcat. Some of the identifiable components, as per the MVC framework are:

• View components, which are implemented using Struts 2 and the GWT framework.

• Model components, which comprise the data layer and the core business logic.

• Controller components that form a framework to support the communication between the view and model components.

The Web Application also exposes specialized web services as a REST API in order to synchronize with the ERP systems. The exposed web services can be accessed using the root URI: {context-path}/rest/sync/{service}/{service-name} Example for calling the authentication service: http://{endpoint}/pdweb-idaho/rest/sync/authentication/authenticate

The references in the web services are explained in another document: Supplier Portal API Guide.

2. Backend

Supplier Portal uses Apache CouchDB as the backend. The development of this application was started with version 1.2. Since then, the Apache team has released many versions, with several features and updates. However, the application will work well with CouchDB, regardless of which version it is. It is recommended to install the latest version available from http://couchdb.apache.org/.

http://couchdb.apache.org/


7

3. Synchronizer

The Synchronizer is a software component that runs within the SAP system and communicates with the Web Application via the web services. For more details, refer to Installing the Synchronizer.

The synchronization can be configured to use either SSL or plain HTTP. The synchronization is always initiated from the Synchronizer in the SAP systems. All connections are outbound. No port needs to be open for an inbound connection to the SAP systems. For security reasons, it is recommended to use SSL. The Supplier Portal web application and CouchDB are physically separated.

Cloud deployment overview This section is meant to be a high-level guide to let you know which tasks are relevant for SaaS deployment.

Tasks When deploying the Supplier Portal as a cloud solution, there is a small portion of work that is not handled by the local implementation teams, but is instead handled by Lexmark’s central SaaS team. The following are some high-level examples:

Task Team

Planning, including the workshop Lexmark PS team

Solution description Lexmark PS team

Installation – SAP Lexmark PS team

Installation – cloud Lexmark Supplier Portal team

Configuration – SAP Lexmark PS team


8

Task Team

Configuration – cloud Lexmark PS team, Supplier Portal team

Synchronization Lexmark PS team

Go-live support Lexmark PS team

Simplified cloud deployment steps The SaaS solution is built on a multi-tenant application, which means that multiple customers use a central pool of application servers and databases.

Tenants are used to separate the use and configuration for each customer. Each tenant has a discrete Web Application configuration and is associated with two databases; one for configuration and one for document storage.

Typically, each customer has three tenants that follow the classic deployment landscape.

• DEV (Development)

• QAT (Quality assurance and testing)

• PRD (Production)

Both the DEV and QAT tenants are hosted under the readsoftdev.com domain, while the production tenant is under the readsoftonline.com domain. For each landscape, the customer will get application access endpoint URLs as sub-domains under the corresponding domain.

• The DEV and QA access URL typically has the following syntax: {deployment-landscape}-{customername}.readsoftdev.com

Example: dev-acme.readsoftdev.com

• The production access URL has the following syntax: {customername}-ap.readsoftonline.com

Example: acme-ap.readsoftonline.com


9

Request a tenant setup

To request a tenant setup, complete the following steps.

1. Send an email to [email protected] with the tenant setup request. Each request should reference the customer ID from Salesforce and include the following information:

Item Notes/Examples

Short name for customer (to be used in the actual tenant names)

To be used in the actual tenant names.

Example: If the customer name is Acme Widgets International, the short name would be acme and the tenant name would be tenant_dev-acme.readsoftdev.com.

System ID This is a value entered in the Synchronizer configuration in SAP and uses a portion of the tenant syntax.

Note: These system IDs must be unique across the entire system; the Cloud/SaaS team will confirm that they are.

Example: If the tenant is tenant_dev-acme.readsoftdev.com, the system ID is dev_acme.

Name that is utilized by the Synchronizer

Typically, the name would be AcmeWidgets Accounts_Payable. The username would be acmeaccountspayable.

Note: This username is not meant to be used by a human being.

The SaaS/cloud team will send you the password that needs to be used in the Synchronizer configuration. These credentials should not be shared, but be used only by the person responsible for configuring the Synchronizer.

2. Provide the key configuration information to the SaaS/cloud team The setup in the database requires the following business-related information:

Item Notes/Examples

Company code numbers, names, and addresses in the scope of the portal

These are used in several areas of the portal and are required to ensure proper operation.

SAP archive document types that will be used for the attachments uploaded in the portal (and for the invoice images sent to the portal)

The portal allows users to upload documents. To bring them into the SAP environment, the portal needs to know what archive document type will be used when they are attached to the PROCESS DIRECTOR and SAP business documents.

It is important that the SAP archive document types are unique to the portal and not used for other business purposes.

Invoice creation options None, MM, MM and FI.

Registration options None, standard self-registration, self-registration with all to workflow, SAML.

Synchronization fields See Data model.

mailto:[email protected]


10

SAML SSO integration with the Supplier Portal

SAML (Security Assertion Markup Language) is an XML- and HTTP-based secure, industry-standard way to perform the Single Sign-On (SSO) function between online applications. The Supplier Portal supports SAML out-of-the-box, which is the preferred way to integrate SSO for the users within your organization, as well as for vendor users.

Customer effort SAML SSO scenarios are not trivial integrations that can be quickly set up, tested, and deployed. Your organization will likely require an IT administrator, who has the required knowledge about SAML SSO, to successfully deploy this SSO solution. The Supplier Portal’s SAML SSO integration solution is developed and tested using Sibboleth, which is the world’s most widely-deployed federated identity solution that supports SAML 2.0. Your organization can also choose to use third-party SAML SSO vendors, such as OneLogin and Salesforce, which simplify the configuration required to deploy SAML SSO.

Certified Identity Providers (IdP) The Supplier Portal’s coverage of the SAML SSO features is developed to allow integration with any authentication provider that supports SAML. We are still in the early phase of supporting this integration. We are also working on also supporting third-party IdPs in the future.

SAML SSO configuration The SAML SSO configuration is described in the SAML settings topic.

SAML SSO terminology SAML SSO has two high-level concepts that are used to identify the systems in the SAML SSO scenario.

• Service Provider (SP): The application the user needs to access; in this case, the Supplier Portal. Supplier Portal customers get their own dedicated endpoint to access a dedicated tenant. Each tenant can be set up as the customer’s dedicated Service Provider.

• Identity Provider (IdP): The sign-on system that will authenticate the user via a username and password, or another verification method.

All SAML SSO scenarios share a common terminology to describe the requests and responses between the SP and IdP.

• Authentication Request (AuthnRequest): A request from the SP to the IdP, made on behalf of the users after they initiate the sign on. The Supplier Portal initiates the sign on when a user clicks the corresponding link or attempts to visit a protected resource, such as a page or file attachment.

• Assertion: An XML document, either part of an IdP's response to an authentication request, or an IdP's unsolicited request to sign a user into an SP, which contains the metadata required to sign on or create a user on the SP.

Supported SSO/SLO scenarios There are two primary SAML SSO scenarios supported by the Supplier Portal. It supports SAML 2.0 SSO with HTTP Redirect-POST binding. Authentication requests from the SP are sent to the IdP as either an HTTP redirect, or as an HTTP Post. Responses or requests from the IdP to the SP are expected to be sent as HTTP Post.


11

SP-initiated SSO SP-initiated SSO is a scenario in which the user starts the sign-on flow from the Supplier Portal, either actively or passively.

Active SSO The user signs into the Supplier Portal by clicking the corresponding signing-in link.

Passive SSO The user visits a private page or file attachment, which they cannot access without authentication.


12

Authenticating with IdP Both the Active and Passive SSO send the user to the IdP for authentication.

IdP-initiated SSO A user is using an internal application that has already been authenticated with the IdP. They click a link that leads to the Supplier Portal site, which begins an SSO session. If needed, a new user is created in the Supplier Portal (or the existing user is found), and the user is logged in.


13

Log out The user actively clicks the corresponding link to log out from the Supplier Portal.

Unsolicited logout request If the IdP and all the SPs in the federated SSO session are configured correctly and the user signs out of any other application in the federated SSO session, the Supplier Portal receives a sign-out request from the IdP and signs the user out of the portal.


14

User information The Supplier Portal grants access to authenticated SSO users, who have one of two basic roles:

• Buyer

• Supplier

To establish an authenticated user context, both user roles require some mandatory user information such as the username and email. The Supplier Portal attempts to extract the following information from the IdP sign-on responses:

• Username (required): The username to log into the Supplier Portal.

The Supplier Portal looks for this value by looking up the UserID attribute name in the IdP sign-on response XML nodes matching. Response/Assertion/AttributeStatement/Attribute/AttributeValue

• Display Name (optional): This information sets the user's display name in the Supplier Portal, which is shown in place of the username. This is often a user-friendly version, such as "Barbara Jones" instead of "bjones."

The Supplier Portal attempts to build a display name from the IdP sign-on response in the following way, using the IdP sign-on response attributes. The attributes are found in the IdP sign-on response XML nodes matching:

Response/Assertion/AttributeStatement/Attribute/AttributeValue

1. Use the display name attribute value from the response XML attribute node, DisplayName.

2. Concatenate the first and last name attribute values from the FirstName and LastName response XML attribute nodes.

3. Set the username as the display name.

• Email Address (required): This sets the user email associated with the authenticated SSO user. This allows the portal to send notifications to users on important events. The Supplier Portal attempts to find the email address by looking up the “Email” attribute name in the IdP sign-on response XML nodes matching. Response/Assertion/AttributeStatement/Attribute/AttributeValue

• Language (optional): This sets the language for localizing the portal to the preferred language of the signed-on user. The Supplier Portal attempts to find the language by looking up the “Language” attribute name in the IdP sign-on response XML nodes matching. Response/Assertion/AttributeStatement/Attribute/AttributeValue

• Phone (optional): This sets the phone number of the signed-on user. The Supplier Portal attempts to find the language by looking up the “Phone” attribute name in the IdP sign-on response XML nodes matching: Response/Assertion/AttributeStatement/Attribute/AttributeValue


15

User information for the Supplier role Warning: This topic is currently under development and not yet available.

For the role of Supplier, an extra set of attributes may be required that allows the portal to determine which groups of suppliers an authenticated user belong to. These are essentially:

• A list of vendor numbers

• Or, a mapping of vendor numbers to the list of business units

Based on the above supplied attributes, the Supplier Portal can directly create a supplier user with other basic user information. This approach involves the customer’s IdP having to authenticate not only the users, but also resolving which suppliers they belong to.

It can be assumed that not all IdPs are capable of proving such information. In such cases, the Supplier Portal offers a set of optional solutions, where a customer IdP handles the authentication, and the vendor relationship is established in the portal via workflows and user validations, to collect the vendor information from the then authenticated users themselves.

Security SAML is a secure protocol that supports encryption and message signing.

• HTTP communication security is ensured by SSL between the IdP and SP.

• Messages can be signed and encrypted to ensure message-level security.

• The Supplier Portal requires that all assertions from the IdP be signed. Signing the assertion allows the portal to verify that the assertion originated at the trusted IdP by validating the assertion's signature against the trusted IdP's public X509 certificate.

• Optionally, supplying the Supplier Portal with a public X509 certificate and private key allows the portal, as the SP, to sign outgoing requests to the IdP, as well as to decrypt assertions from the IdP.

• To take advantage of these security features, the IdP must be configured to validate signatures and encrypt assertions by using the same private key and public X509 certificate that the Supplier Portal uses to sign the outgoing requests to the IdP.

• The Supplier Portal signs outgoing messages to the IdP with the SHA1 hashing algorithm. The portal supports incoming messages from the IdP, signed with the SHA1 or SHA256 hashing algorithm.

• The Supplier Portal can decrypt assertions from the IdP, encrypted with the AES-128, AES-256, or Triple DES encryption algorithm.

• User passwords are never transmitted as part of an SAML authentication request or response. A signed authentication request indicates that a new user should be created. This request contains only the username and any additional metadata (name, email address, etc.) that was configured by the IdP administrator.


16

Install the Synchronizer

General concepts The synchronizer is responsible for sending and receiving data from the ERP system to the Supplier Portal. The synchronizer is located inside the ERP system and calls out to the Supplier Portal to begin its work.

Synchronizer activity is categorized by document type.

• Invoices (document originates from the ERP system)

• Incoming invoices (document originates from the Supplier Portal)

• Purchase orders (document originates from the ERP system)

• Vendor master data (data originates from the ERP system)

• Vendor master change request (data originates from the Supplier Portal)

Pre-installation The Supplier Portal Synchronizer can be installed on any ERP system with SAP_BASIS >= 620 and having the latest supported PROCESS DIRECTOR Accounts Payable version (/COCKPIT/VER transaction) installed.

Installation Import the request in the STMS transaction.

Note: With the SAP_BASIS 702 version, a new feature has been added to the TMS system. The transport control program (tp) checks the component version of the transport that is released and the component version of the system to which the transport is going to be imported. If there is a difference, this difference is highlighted in the import queue (STMS_IMPORT TRANSACTION). If you then try to import the transport, the import will display a warning message about the difference in the SAPCOMPONENT versions.

Resolution • Ideally, the component versions of the source and target systems should match.

• If that is not possible and you still wish to import the transport request, you can bypass the warning with the import option, Ignore invalid component version. You can see this option in the Options tab upon importing.

• Alternatively, if you are doing the import via the command line, you can use the mode, u4. For example: tp import <TR> <SID> u4.

• You can also limit the check for certain components. Please see SAP note #1742547 under the Configuration: Component inclusion and exclusion section (SAP note #1756116 corrects a program error with that function).

• Finally, if you wish to turn off this function, you can do so with the transport parameter, SP_TRANS_SYNC = OFF. You can add this via STMS > Systems Overview > <SID> > Transport Tool Tab > Change Mode. Ensure that you do this from the domain controller.


17

Post installation Run the /COCKPIT/GC_RICK transaction.

Create missing indexes with the SE11 transaction, if required. Implement the required EMEIC corrections to PROCESS DIRECTOR Accounts Payable.

Indexing The Synchronizer program requires specific indexing in the CDHDR table. The following fields must be indexed:

• MANDANT

• OBJECTCLAS

• UDATE

• UTIME (optional)

It is recommended that you create an index (MANDANT, OBJECTCLAS, UDATE) as described in SAP note 573864.

This index is shipped by SAP with the ERP 6.0 EHP5 release, as CDHDR~003.

If you have ERP 6.0 EhP5 or a higher release, make sure that the CDHDR~003 index in the CDHDR table is active in DDIC and the database.

Index creation is not required on an SAP HANA system.

• SAP note 573864 - CD: Select in CDHDR, without an index

• SAP note 856624 - Indexes for the CDHDR table (SAPKB62050/51, SAPKB64011)

• SAP note 884534 - CD: Two CDHDR table indexes, with the "no database index" option

• SAP note 1271166 - CD: CHANGEDOCU_WRI performance selection control parameter

Install certificates The Synchronizer program typically requires a secure connection to the Supplier Portal. For correct Synchronizer operation, the SAP system requires that a proper certificate chain be established to validate the security certificate in use.

In the case of cloud-delivery solutions, two certificates are in scope. One for the development (DEV), quality assurance and test (QAT) instances, and another for the production instance (PRD).

• DEV – readsoftdev.com certificate

• QAT – readsoftdev.com certificate

• PRD – readsoftonline.com certificate


18

Install in STRUST 1. Enter the STRUST transaction.

2. Double-click the SSL client SSL Client (Standard) node.

3. Import the certificate by clicking the button in the Certificate section.


19

4. Then, click Add to Certificate List.

Configure the Synchronizer You can get to the Supplier Portal Synchronizer configuration by either clicking Setup in the /COCKPIT/GC_SYNC transaction or via the /COCKPIT/GC_CI transaction.

Basic settings These are the minimum settings required to run the Supplier Portal Synchronizer.

Define connection The parameters for the connection can be set up in the /COCKPIT/GC_C1 transaction.


20

Connection parameters

Setting Description

Connection Name of connection

Destination Destination of type G (HTTP connections to the external server) in the SM59 transaction

If the Destination parameter is filled in, the Host Name, Port no. and SSL port no. parameters can be blank

Host Name Host name of the Supplier Portal tenant

Port no. Port number for non-secure connection

SSL port no. Port number for secure SSL/TLS connection

HTTP script URI for web service

Usually, pdweb-idaho/rest/sync

Username Username for web service

Password Password for web service

ERP sys ID ERP system ID; if the field is kept empty, the system ID from the SAP system is taken


21

Define IV settings The Process Director AP settings can be set up using the /COCKPIT/GC_C8 transaction. You can then configure the support of the new Supplier Portal notes and/or the old WEB BOARD notes. The WEB BOARD notes are needed only in case the customer is moving from WEB BOARD to the Supplier Portal. If it is a new installation, it is recommended that you use the Supplier Portal notes.

Define PO settings The purchase order synchronization setting can be set up by using the /COCKPIT/GC_C2 transaction.

Configuration Description

Version Mngt If SAP purchase order Version Management is activated, this flag needs to be set.

SAP purchase order Version Management enables you to generate and manage versions of purchase requisitions and external purchasing documents, such as purchase orders.

Release Proc If SAP purchase order Release Procedure is used, this flag needs to be set.

Define MA settings The vendor master data settings can be set up by using the /COCKPIT/GC_C12 transaction. Within this configuration, the bank data can be scrambled during the synchronization so that the bank data is not fully visible in the Supplier Portal.

Bank number Visible data

12345678 ****5678

1234567 ***4567

123456 **3456

Example of scrambled bank data

Define MC settings The vendor master change request settings can be set up by using the COCKPIT/GC_C11 transaction. Here, it is possible to configure the mapping from the Supplier Portal to PROCESS DIRECTOR vendor master. Before setting up the mapping, a configuration needs to be set in /EBY/PDBOC for vendor master. For more information, refer to the Process Director SAP Configuration Guide.


Object type PROCESS DIRECTOR object type - For the vendor master change request, it must be MD_VENDOMA (object type for PROCESS DIRECTOR vendor master).


22


Origin Origin of the data - Check in the /EBY/PDBOC transaction to determine which origin is maintained for the Supplier Portal.

Mapping ID The mapping ID used in /EBY/PDBOC to map the vendor master data from the Supplier Portal to PROCESS DIRECTOR.

In case the Supplier Portal environment does not yet exist in PROCESS DIRECTOR, create a new environment called SP – Supplier Portal in /EBY/PDBOC (see the PROCESS DIRECTOR SAP Configuration Guide) and create the following external data model for the newly created environment.

Origin Node ID Parent Logical level

SP (Supplier Portal) SINGLEITEM HEADER

SP (Supplier Portal) BANKDATA SINGLEITEM BANK

Example mapping:

Origin Map ID Node ID Parent Logical level Field name External field name

SP <MAPID> SINGLEITEM HEADER ACTIVITY ACTIVITY

SP <MAPID> SINGLEITEM HEADER ANRED TITLE

SP <MAPID> SINGLEITEM HEADER BUKRS COMP_CODE

SP <MAPID> SINGLEITEM HEADER KTOKK ACCOUNT_GROUP

SP <MAPID> SINGLEITEM HEADER LAND1 COUNTRY_KEY

SP <MAPID> SINGLEITEM HEADER LIFNR VENDOR_NO

SP <MAPID> SINGLEITEM HEADER NAME1 NAME1

SP <MAPID> SINGLEITEM HEADER ORT01 CITY

SP <MAPID> SINGLEITEM HEADER PSTLZ POSTCODE

SP <MAPID> SINGLEITEM HEADER SORT1 SEARCH_TERM1

SP <MAPID> SINGLEITEM HEADER STRAS STREET_NO

SP <MAPID> BANKDATA SINGLEITEM BANK BANKL BANK_KEY

SP <MAPID> BANKDATA SINGLEITEM BANK BANKN BANK_ACCT

SP <MAPID> BANKDATA SINGLEITEM BANK BANKS BANK_CTRY

SP <MAPID> BANKDATA SINGLEITEM BANK BUKRS COMP_CODE


23

Origin Map ID Node ID Parent Logical level Field name External field name

SP <MAPID> BANKDATA SINGLEITEM BANK LIFNR VENDOR

SP <MAPID> BANKDATA SINGLEITEM BANK WAERS WAERS

Define upload The parameters for the connection can be set up in the /COCKPIT/GC_C3 transaction.

Activate the document types that are transferred from PROCESS DIRECTOR Accounts Payable to the Supplier Portal, and from invoices/credits in the Supplier Portal to PROCESS DIRECTOR Accounts Payable.

Note: The same settings need to be made on the Supplier Portal side (see Step: Provide key configuration information to the SaaS/cloud team).

Example of upload entries

Upload parameters

Parameter Document type

Object type II = Incoming invoice IV = PROCESS DIRECTOR Accounts Payable PO = Purchase order (not yet supported) MA = Master data (not yet supported) MC = Master data change request (not yet supported)

Document type Any document type from the OAC2 transaction, which is set up in use with /COCKPIT/B or /COCKPIT/I, in the OAC3 transaction.


24

Advanced settings

Redefine document types

In the /COCKPIT/GC_C10 transaction, it is possible to redefine document types to custom development classes. A customer development class should inherit from the original class: /COCKPIT/CL_GC_XX_SYNCHRONIZER where XX is II, IV, MA, MC, or PO, for the selected object type. This option allows you to adjust the standard synchronization to a custom one.

Note: If the standard class is redefined to a custom class in order to map custom or more fields than those in the standard, within the portal configuration, it is necessary to add those fields to the view (see Step: Provide key configuration information to the SaaS/cloud team).

Manage customizing

Initial consistency check See the Post installation topic for more detailed information.

Edit synchronization markers A synchronization marker is an entry that is calculated based on the selection screen, with the timestamp of the last synchronization. Another incremental synchronization will use this timestamp to reduce the synchronized data. Every object type has its own syncmark. The empty filter hash field is for the default selection screen (no additional filters). Whenever the selection screen is adjusted, a new synchronization marker is calculated.

Synchronization markers can be edited in the /COCKPIT/GC_C4 transaction. This is usually not needed, but in case an incremental synchronization fails with the Last incremental run for XY not found error message, a synchronization mark can be added.

Another solution is to set the synchronization marker in the /COCKPIT/GC_SYNC transaction.

1. Go to the /COCKPIT/GC_SYNC transaction.

2. Select the process types for which you get the Last incremental run for XY not found error message.

3. Enter %syncmark_add in the command field.

4. Enter or select a date in the next popup.

5. Check the /COCKPIT/GC_C4 transaction to determine if a synchronization marker has been set for the selected process types.

Edit error queue In the edit error queue, you can see which documents failed to synchronize. Those documents will be processed again in another incremental synchronization. The list of documents can also be edited.


25

Run the Synchronizer in SAP When implementing the Supplier Portal, perform the following general steps.

1. Establish a connection to the Supplier Portal.

2. Configure the attachment types that need to be synchronized.

3. Determine the document selection for the initial synchronization.

4. Execute the initial synchronization.

5. Set a sync mark.

6. Schedule incremental synchronizations.

You can check how much will be synchronized by using the simulate selection option. Before you do the full synchronization using some selection, please add synchronization marks before (refer to the Edit synchronization markers topic). You can check the markers in the /COCKPIT/GC_C4 transaction. If they have not been created, the incremental synchronization will throw an error. The empty filter hash is for the default selection screen.

If there is any selection, the filter hash is calculated. After the initial synchronization, the program should work as a periodical job, with the same selection in incremental mode.

The operator can execute the Supplier Portal Synchronizer with the /COCKPIT/GC_SYNCHRONIZER program, or the /COCKPIT/GC_SYNC transaction.


26

Destination Choose the connection from /COCKPIT/GC_C1.


27

Selection

Selection parameters

Parameter Description

Incremental synchronization II = Incoming invoice IV = PROCESS DIRECTOR Accounts Payable PO = Purchase order MA = Master data MC = Master data change request

The II and MC process types are not incremental as these represent documents created in the Supplier Portal.

Simulate selection and stop Run a selection query to present a report on the number of documents that will be synchronized (simulated; not actually synchronized).

It is recommend that you run a simulation before a big initial synchronization to check how many documents will be processed.

Supplier Limit the selection to the supplier in PD AP/purchase order/master data.

Company code Limit the selection to the company code in PD AP/purchase order.

Account group Limit the selection to the account group in PD AP/purchase order/master data.

Order type Limit the selection to the order type of the purchase order.

PROCESS DIRECTOR doc. type PROCESS DIRECTOR AP document types. Refer to the PROCESS DIRECTOR Accounts Payable Configuration Guide for more details.

No. of parallel processes Number of parallel processes running at the same time.

Max. no. of objects Number of objects that are processes in a single task.


28

Synchronization Activate the document types that will be synchronized between the ERP and the portal.



PROCESS DIRECTOR AP II = Incoming invoice IV = PROCESS DIRECTOR Accounts Payable PO = Purchase order MA = Master data MC = Master data change request

Purchase order Synchronize purchase orders with the Supplier Portal.

Incoming invoice Synchronize new invoices in the Supplier Portal with PROCESS DIRECTOR Accounts Payable.

Vendor master data Synchronize vendor master data with the Supplier Portal.

Vendor master change request Synchronize vendor master change requests from the Supplier Portal, with the vendor master in PROCESS DIRECTOR.

Activate filter Activate an additional filter for PD AP/purchase order/incoming invoice/vendor master data; this switch is available only if incremental synchronization is not active.

Additional filters for PROCESS DIRECTOR Accounts Payable


Document number Document number (DOCNO)

Document date Document date (DOC_DATE)

Creation date Creation date (CR_TIMESTAMP)

Additional filters for purchase orders


Purchasing document Purchasing document

Order type Order type

Document date Document date


29

Additional filter for incoming invoices


Vendor Vendor number

Additional filters for vendor master data


Supplier Supplier number

Account group Account group

Include deleted records Includes deleted records

Initial synchronization When first implementing the Supplier Portal, a one-time initial synchronization must take place to bring invoices, purchase orders, and vendor master data from the SAP system to the Supplier Portal.

This use of the Synchronizer differs from its normal use, primarily by the Incremental synchronization flag being deselected, which opens up a further selection criteria area in the Synchronizer interface. This allows date-based selections of invoices and PO documents.

When the Incremental synchronization flag is not used, an additional selection criteria area becomes available. Open this additional selection area by selecting the Activate filter check box.


30

Incremental synchronization After the initial synchronization has been executed, the subsequent synchronizations will be incremental. Incremental synchronization offers selection criteria that are different from those for the initial synchronization.

Check data consistency The Synchronizer can be used in conjunction with the Supplier Portal database to test if they have sent and received document data.

Testing can confirm that the synchronization process has selected the correct fields for synchronization and that the database has properly received the data.

Field selection The Synchronizer loads fields into a field catalog from the SAP system, and then queries the Supplier Portal as to which fields should be synchronized. This activity can be reviewed by operating the Synchronizer with the log level set to DEBUG (level 5).

To inspect the activity, first, examine the fields loaded into the field catalog by selecting a document type, setting the log level to 5, and then triggering the synchronization on at least one document. The resulting log file reveals the fields loaded into the catalog.


31

The second action of the Synchronizer is to query the web service of the Supplier Portal to determine which fields should be synchronized. This can also be viewed in the log file.

To understand whether the selection is correct or not, you need to compare the log file with the view selection in the database. Please contact the Supplier Operations team for the configuration on the Supplier Portal side.


32

Data check To check that the data transmission has been successfully executed without any errors, you need to examine the source document and compare it to the database values after the synchronization.

Further examination in the user interface can also confirm that the values are correct. However, this has a limitation in that the user interface does not show all the values synchronized as some fields are in use for logical reasons, but have no display purpose.

In short, you can view the source document information either directly on the ERP database or in the TEKKI service transaction in the PROCESS DIRECTOR interface, and then compare those values with the Supplier Portal’s database.

Logging Use the following parameters to activate logging.

Logging parameters


Parameters Print all the used parameters in a log

Log level Log level

0 = Abort 1 = Error 2 = Production (default, recommended) 3 = Performance 4 = Warn 5 = Info 6 = Debug

Verbose Print additional information like timestamp and message class

Include Statistics Print statistics at the end of the log


33

Debugging Use the following parameters to activate debugging. This area can be shown/hidden by entering %EXPERT/%DUDE in the transaction code field.

Debugging parameters


Debug mode (synchron) Deactivate parallel task execution

Verbose Print additional information like timestamp and message class

Dump HTTP requests Activate the dump of HHTP requests

Path for HTTP dump files Path for the HTTP dump files

Release information Click to view the release information about the installed Supplier Portal Synchronizer version.


34

Synchronize search helps Search helps in the Supplier Portal can be created/updated/deleted with the /COCKPIT/GC_SRCHHELP transaction or the /COCKPIT/GC_SEARCHHELP program.

Note: In most cases, adjustments need to be made in the Supplier Portal to support the search help. Please check with the Supplier Portal DevOps team before synchronizing the search help to determine if it is supported in the standard Supplier Portal.

Parameters

Destination Choose the connection from /COCKPIT/GC_C1.

Selection



Object type Object type

II = Incoming invoice IV = PROCESS DIRECTOR Accounts Payable PO = Purchase order MA = Master data

Header field Header field in the Supplier Portal

Table name DDIC table name for the data table

Create Create search help

Update Update search help

Delete Delete search help

Logging Refer to Logging in the Run the Synchronizer in SAP topic.

Debugging Refer to Debugging in the Run the Synchronizer in SAP topic.


35

Synchronize dynamic discounting settings Warning: Dynamic Discounting is not yet supported in the Supplier Portal.

Dynamic discounting settings can be created/updated with the /COCKPIT/GC_DYNDISC transaction or the /COCKPIT/GC_DYNAMIC_DISCOUNT program.

Parameters

Destination Refer to Destination in the Run the Synchronizer in SAP topic.

Logging Refer to Logging in the Run the Synchronizer in SAP topic.

Debugging Refer to Debugging in the Run the Synchronizer in SAP topic.

Background jobs The following background jobs can be run in the background:

• /COCKPIT/GC_SYNCHRONIZER program

The Supplier Portal Synchronizer can be scheduled as a background job with the /COCKPIT/GC_SYNCHRONIZER program.

• /COCKPIT/GC_SEARCHHELP program

Regular Supplier Portal search help updates can be scheduled as background jobs with the /COCKPIT/GC_ SEARCHHELP program.

• /COCKPIT/GC_DYNAMIC_DISCOUNT program

Dynamic discounting settings can be scheduled as background jobs with the /COCKPIT/GC_DYNAMIC_DISCOUNT program.


36

Configure the Supplier Portal The Supplier Portal offers a variety of configuration options in the browser, for use by appropriate administrative users.

Not every configuration option is available in the browser interface. The configuration choices that are not available through the browser interface are changed by a consultant, who has access to the underlying infrastructure. This includes items like the configuration between the application server and the database, the field catalog that controls the data that will be synchronized, and the field profiles that control the visibility of the information in the browser.

Logon page info text This allows the editing of the login information section. The login information section can be maintained in different languages.


37

General settings

Name Name for the login page information text

Layer • DEFAULT The default/standard layer

• SYSTEM From SAP (not applicable here)

• CUSTOMER Custom layer for the specific tenant

Start date Start date for the login page information text

End date End date for the login page information text

Information pages You can also maintain the existing information pages. Existing entries can be edited by clicking the content column. A popup is displayed, where the information can be adjusted. The UI provides a WYSIWYG editor.

It is also possible to add an information page in a language that does not already exist in the portal. This can be done by clicking the Add button. A new line will be created, where the language can be selected and the content can be entered/adjusted.

It is also possible to delete existing information pages.

If a user opens the Supplier Portal login page in a language where the information page is missing, the information page is displayed in the default language, English.

Information pages

Language Language for the information text

Content Content of the information text


38

Terms of service

General settings

Name Name of the terms of services pages




Company codes This configuration allows you to edit the company code information that is used in invoice creation.

Note: This should be maintained along with the company code selection in the Synchronizer parameters.


39

Email templates This configuration allows you to edit the email templates that are used, for example, for password reset emails, and notification emails. You can also create new templates, if required.

Possible configuration for email templates:

General settings

Name Name of the email template

Description Description of the email template





40

Email templates

Language Language of the email template

Subject Subject of the email template

Email text Content of the email

List of email templates The following email templates are available in the standard configuration.

Template name Purpose

activateUser Used for activating inactive users

associateVendorApprove Approval email when an additional vendor number assignment workflow fails validation, and has then been approved in workflow

associateVendorReject Rejection email when an additional vendor number assignment workflow fails validation, and has then been rejected in workflow

importUser Activates uses in bulk

InvoicePaid Notifies suppliers that their invoice has been paid

InvoiceRejected Notifies suppliers that their invoice has been rejected

InvoiceSubmitted Notifies suppliers that their invoice has been submitted to the Accounts Payable department

NewNote Notifies suppliers that their invoice has a new message from the Accounts Payable department

NewPurchaseOrder Notifies suppliers that a new purchase order is available in the portal

newUser New user created by the administrator (from the portal)

preResetPassword Initial email, with a link to trigger a password reset

registrationWorkFlowTrigger Self-registration email notification to the supplier user on workflow start

resetPassword Second email in the reset password process, containing the initialized password

userActivation Notification to buyer admin that a failed self-registration needs to be handled

userRegister Self-registration success email

userReject Rejection email when a self-registration workflow has been rejected


41

Template name Purpose

wfreceipt Generic workflow step notification

wfreceiptDataChanget Used for vendor master data changes

Placeholders Email templates use placeholders. The following placeholders can be used. When the email is generated, the placeholders are replaced with actual values.

USERS

Placeholder Purpose

$user.name First and last names of the receiver of the email

$user.username Username of the receiver of the email

$user.password Initialized password generated during new registrations and password resets

$document.name Used to display the name of the current user doing a workflow action

$document.email Used to display the email address of the current user doing a workflow action

APP LINKS

Placeholder Purpose

$link.applink URL link to the portal; fixed in the configuration

$link.confirmlink Link with random key; used when resetting passwords

WORKFLOW

Placeholder Purpose

$wf.NAME Name of the workflow used in the current action

DOCUMENTS

Placeholder Purpose

$document.DOCNO Portal ID number (equals the document number in PROCESS DIRECTOR)


42

Placeholder Purpose

$document.VENDOR_NO Vendor number contained in the invoice

$document.REF_DOC_NO Invoice reference number

VENDOR

Placeholder Purpose

$document.VENDOR Vendor number

SETTINGS

Placeholder Purpose

$settings.customer.name Name of the customer/tenant

$settings.customer.site.link Link to the customer’s/tenant’s website

OTHER

Placeholder Purpose

$link.singledoclink Single document link; used to directly take the user to a specific document or workflow step

System id white list You can configure which SAP instances are allowed to synchronize with the Supplier Portal tenant. If no SAP instance is maintained, the first one that synchronizes with the Supplier Portal tenant is automatically added to the white list. Further SAP systems need to be manually added.


43

Portal settings

Email settings You can configure the email account settings for outgoing emails. This is the same concept as when manually configuring an email address in any other email client (for example: Thunderbird, Outlook).

Setting Description

Sender name The sender name for the outgoing emails (e.g. Acme Accounts Payable)

Sender username Username to connect to the email server

Email sender password Password of the sender

Sender address The sender email address (e.g. [email protected])

Use Authentication Needs to be activated if the outgoing STMP server requires user authentication

SSL/TLS Encryption Needs to be activated if you require a secure connection via the SSL/TLS

SMTP host server Host name or IP address of the SMTP server

SMTP server port Server port of the SMTP server

Email header Generic email header that is added to each outgoing email

Email footer Generic email footer that is added to each outgoing email

General The following are some generic settings for the Supplier Portal tenant.

Info

Setting Description

Supplier Portal URL URL of the Supplier Portal tenant (Example: https://acme-qa.readsoftdev.com/pdweb-idaho/).

Name of Buyer Name of the buyer company (Example: Acme, Inc.).

Link to buyer’s homepage Link to the buyer’s homepage.

mailto:[email protected]


44

Setting Description

Show customer logo or banner • Logo: Show the logo on the login page. The logo needs to be

uploaded first by using the Attachments icon.

• Banner: Show the banner on the login page. The banner needs to

be uploaded first by using the Attachments icon.

• None: None of the above.

Display name for document notes The display name when notes are created in PROCESS DIRECTOR and synchronized with the Supplier Portal.

Document type-specific settings

Setting Description

Invoices

Invoice creation mode This configuration determines whether general expense (FI) invoices can be created in the Supplier Portal or not.

• No invoice creation

Invoice creation is not possible.

• Only PO based invoice creation

Only invoices based on purchase orders can be generated.

• PO based and general expense invoice creation

Purchase order-based and general expense invoices can be created.

Main invoice image • Generated PDF on document submit The image that is generated when a document is submitted is used as the main invoice image. In this case, the Generate image on document submit configuration option must be set.

• First image uploaded The first uploaded attachment will be used as the main invoice image.

• First image uploaded by the Upload Invoice button The first attachment that is uploaded using the Upload Invoice button will be used as the main invoice image.

• Nothing No attachment will be used as the main invoice image.

Generate image on document submit With this configuration, a PDF is generated, based on the entered data.


45

Setting Description

Vendor Master Data

Vendor Master change mode If the Vendor Master change mode is set to either Execute portal-side workflow or to Create change request, changes to vendor master data records can be initiated from the portal.

• No changes allowed

It is not allowed to change vendor master data records in the portal.

• Execute portal-side workflow

Changes to vendor master data records need to be approved in the portal, using the workflow selected for the Data Change workflow ID setting.

• Create change request

A request to change vendor master data records is created and sent to PROCESS DIRECTOR.

Data Change workflow ID Using this setting, a workflow can be selected to approve data changes in the Supplier Portal. This setting is applied only, if the Vendor Master change mode is set to Execute portal-side workflow.

Note: Do not select a workflow if PROCESS DIRECTOR is to be used for vendor master data changes.

Password settings

Setting Description

Use password policy Activation of the password policy.

Password Minimum Length Minimum password length. For security reasons, it is not recommended to support a password with less than 8 characters.

Minimum upper case character Minimum number of uppercase characters required in the password.

Minimum number of lower case characters

Minimum number of lowercase characters required in the password.

Minimum Numeric characters Minimum number of numeric characters required in the password.

Minimum special characters Minimum number of special characters in the password.

Allowed special characters List of allowed special characters (E.g. !,.#*-()).

Check password expiration Configuration that the password expires after a certain number of days.

Password expiration in days Password expiration period in days.


46

Setting Description

Warning before password expires in days

Days before a warning is presented to the user that the password is due to expire.

Check initial password expiration Configuration to check the expiration of the initial password.

Initial password expiration time in hours

Expiration time in hours before the initial password expires.

Check for a wrong password entered Configuration to check for a strong password.

Maximum password attempts Maximum number of attempts allowed to enter a password before the user account gets locked.

Self registration settings

Settings Description

Hide self-registration links Hides the self-registration link for users.

Vendor approval workflow Workflow to approve newly registered supplier users.

Buyer approval workflow for admin users

Workflow to approve newly registered buyer admin users.

Buyer approval workflow for non-admin users

Workflow to approve newly registered non-admin buyer users.

Buyer approval workflow for vendor association

Workflow to approve supplier users who need to be registered with a certain vendor.

Vendor approval required Configuration to determine if the supplier user registration needs approval in all cases.

Buyer approval required Configuration to determine if the buyer user registration needs approval in all cases.

Email template for user activation Email template for user activation.

Email template for new registered users

Self-registration success email.

Email template for approving vendor association

Approval email when an additional vendor number assignment workflow fails validation, and is then approved in a workflow.

Email template for rejecting vendor association

Rejection email when an additional vendor number assignment workflow fails validation, and is then rejected in a workflow.

Email template for rejected registration of a new user

Rejection email when a self-registration workflow is rejected.


47


Email template for notifying vendor on workflow

Notification email to be used for informing a vendor when the validation process is in workflow.

Captcha background color Background color for Captcha on the registration screen.

Captcha Script Color Text color for Captcha on the registration screen.

Allowed invoice states for selfregistration

Invoice states that are allowed for self-registration.

Supported values:

• B16 - Under review

• B17 - Free for payment

• B18 - Paid

Registration workflow trigger condition

• All (Registration: Success/Failure) All registrations (successful/erroneous) need to be approved in a workflow.

• On registration failure Registration workflow is required only if a registration was erroneous/ambiguous.

User handling setting

Setting Description

Email template for reactivating user Used for activating inactive users.

Email Template for activating imported users

Used for users who have been imported using the import function in the Supplier Portal.

Email template for creating new user Email template for users created by an administrator.


48

SAML settings You need the following information about your SAML SSO Identity Provider:

• Entity ID (required): The unique identifier for your IdP. The Supplier Portal accepts SAML assertions only from this ID.

• Single Sign On Service (required): The SSO endpoint that the Supplier Portal sends authentication requests to.

• Single Logout Service: The SLO endpoint that the Supplier Portal sends logout requests to.

• Public X.509 Certificate (required): The Supplier Portal uses this to establish trust with your IdP. With this certificate, the portal validates any incoming SAML assertions from the IdP.

When you have all the required information, you can log in to the portal with administrator rights and configure the SAML settings by selecting the Configuration > SAML settings sub-category in the Worklist.

SAML SSO setup and IdP configuration To configure IdP-specific settings, in the Worklist, select the Configuration > SAML settings > SAML SSO Setup and IdP Configuration sub-category and enter the following general settings.

Setting Description

Enable single Sign-On with SAML Select this check box to enable SAML SSO using the SSO login URL.

Identity Provider Entity ID (required) The unique identifier for your IdP; the Supplier Portal accepts SAML assertions only from this ID.

Login URL (required) The SSO endpoint that the Supplier Portal sends authentication requests to.

Logout URL The SLO endpoint that the Supplier Portal sends logout requests to.

Identity Provider X.509 Signing Certificate

The Supplier Portal uses this to establish trust with your IdP. With this certificate, the portal validates the incoming SAML assertions from the IdP.

Federation Metadata Document Links to the SAML SSO Service Provider Metadata XML document; this is available after you save a valid SAML SSO configuration.

SAML Profile/binding - Request Profile binding used by the SP to make an authentication request to the IdP; the Supplier Portal supports two types of profile binding:

• urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect

• urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST


49

SAML SSO Service Provider configuration To configure service provider-specific settings, in the Worklist, select the Configuration > SAML settings > SAML SSO Service Provider Configuration sub-category and enter the following general settings.


Service Provider Entity ID (required) The unique identifier for your IdP; the Supplier Portal accepts SAML assertions only from this ID.

Name ID Format Any format is supported. However, the preferable NameID format is:

urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

This is preferred in nearly every scenario. Persistent usernames ensure that the identity between the Supplier Portal and the IdP never changes.

SP X.509 Private Key Used to sign requests to the IdP, and decrypt responses from it. If no key is supplied, the Supplier Portal will not sign requests or process any encrypted Identity Provider responses.

SP X.509 Certificate Used to validate the outgoing request signatures from the Supplier Portal to your Identity Provider, as well as to validate and decrypt responses.

The signing key for this certificate should be included in the Service Provider Private Key field. If no certificate is supplied, the Supplier Portal does not sign requests or process any encrypted Identity Provider responses.

Service Provider Private Key and x.509 certificate This is an optional Service Provider certificate/key pair that allows the SAML requests to be signed and/or encrypted (if the IdP supports decryption). If you do not have a private key and public certificate to use for the SAML SSO, you can generate your own pair with a UNIX-like system and OpenSSL.

Note: As a certificate/key pair can be generated on any UNIX system, the Supplier Portal does not provide a Service Provider certificate/key pair. Customers who wish to utilize this option for their configuration will need to provide their own certificate/key pair. This allows customers to determine the strength of the encryption key, based on their organization's needs.

A self-signed certificate works for this option. Please perform the following steps to generate a self-signed certificate in a UNIX environment.

1. To begin with, you need to generate the root CA key (this is what signs all the issued certificates). openssl genrsa -out rootCA.key 2048

2. Generate the self-signed (with the key previously generated) root CA certificate. openssl req -x509 -new -nodes -key rootCA.key -days 365 -out rootCA.crt


50

Workflow configuration Within the workflow configuration, it is currently not possible to create your own workflows or to change the name or description of a workflow.

Within each workflow, it is possible to add workflow step processor groups or individual workflow processors. To do this, select a workflow by clicking the workflow name. On the next screen, you can add new processor groups by clicking the Add processor group button. New individual processors can be added by clicking the Add processor button. It is also possible to delete existing workflow processor groups or individual workflow processors.

Workflow step configuration Within the workflow step configuration, changes are not possible. However, the different workflow steps are listed here with descriptions.

Workflow recipient groups Within this configuration, it is possible to create, maintain or delete workflow recipient groups.

Creating workflow recipient groups To create a new workflow recipient group, click the Create workflow recipient group button. On the next screen, select a template (e.g. Default) and click Create from template. You can then enter a name for the workflow recipient group and assign users to it. Click the Add processor button to add users.

Maintaining workflow recipient groups An existing workflow recipient group can be maintained by clicking its name. On the maintenance screen, it is then possible to change the name of the workflow recipient group and maintain (add or delete) users.

Copying workflow recipient groups Existing workflow recipient groups can also be copied. This can be done by selecting a workflow recipient group and clicking the Copy button. In the displayed popup, enter a name for the new recipient group. The copied group will contain the same workflow processors as the original workflow recipient group.

Deleting workflow recipient groups Workflow recipient groups can be deleted. This can be done by selecting the workflow recipient group and clicking the Delete button. However, before deleting a group, please make sure that the workflow recipient group is not used in any workflow.

Workflow notification configuration Within this configuration, no changes are allowed.


51

Groups maintenance Within this configuration, it is possible to create, delete, change, and copy groups. The idea behind the groups is to tweak the behavior of some user groups. For example, it is possible to create a group that has access to documents (Invoices, Purchase Orders, Vendor Master) of a certain company code only.

Add groups To create a group, click the New button. On the next screen, you can enter a name for the group, select a Worklist for that group, and grant access to different document types by clicking the Add doc-type button. Furthermore, for each document type, restrictions can be defined. To view the restriction definition for a document type, select it and click the Access restriction fields button. To add a restriction field, click Add field. Enter the Fieldname (which is the internal field ID) a Type, and an allowed Fieldvalue. Possible values for Type and their corresponding formats for Fieldvalue are:

• Value: Use one specific value for Fieldvalue. In case of a numeric value, use a . (dot) as the decimal separator.

• Values: Use a list of specific values separated with a , (comma) for Fieldvalue. For numeric values, use a . (dot) as the decimal separator.

• Interval: Use an interval for Fieldvalue, typing first the start value, followed by the end value of the interval. Both values should be separated with a – (dash). For numeric values, use a . (dot) as the decimal separator.

Note: All the values for the different fields within one document type are combined with a logical AND, meaning that the documents are visible only if they meet all the criteria entered.

Maintain groups An existing group can be maintained by clicking its name. On the maintenance screen, it is then possible to change the Worklist of the group and maintain (add, change, or delete) access to the document types and their restrictions.

Copy groups Existing groups can also be copied. This can be done by selecting a group and clicking the Copy button. In the displayed popup, enter a name for the new group. The copied group will have the same access to documents as the original group does (including the restrictions).

Delete groups Groups can be deleted. This can be done by selecting the group and clicking the Delete button. However, before deleting a group, please make sure that this group is not used in any user account.


52

Data model

PROCESS DIRECTOR Accounts Payable The data for PROCESS DIRECTOR Accounts Payable documents is retrieved by the /COCKPIT/API_DATA_GET function module.

E_STR_HEADER HEADER

INVOICE_GUID Unique document identification

ORIGIN Origin of PROCESS DIRECTOR document

DOCNO PROCESS DIRECTOR document number

FI_MM_FLG FI or MM document

STATUS Document status

INVOICE_IND Flag to identify document as invoice

CP_DOC_TYPE PROCESS DIRECTOR document type

DOC_TYPE Document type

DOC_DATE Document date in document

VENDOR_NO Account number of vendor or creditor

DIFF_INV Different invoicing party

PO_NUMBER Purchasing document number

PSTNG_DATE Posting date in document

FIS_PERIOD Fiscal period

REF_DOC_NO Reference document number

COMP_CODE Company code

GL_ACCOUNT G/L account number

CURRENCY Currency key

GROSS_AMOUNT PROCESS DIRECTOR gross amount

NET_AMOUNT PROCESS DIRECTOR net amount

CALC_TAX_IND Automatic tax calculation


53

E_STR_HEADER HEADER

BLINE_DATE Baseline date for due date calculation

PMNTTRMS Terms of payment key

DSCT_DAYS1 Cash discount day 1

DSCT_DAYS2 Cash discount days 2

NETTERMS Net payment terms period

DSCT_PCT1 Cash discount percentage 1


PYMT_METH Payment method

HEADER_TXT Document header text

DEL_COSTS Unplanned delivery costs

DEL_COSTS_TAXC Tax code for delivery costs

EXT_DOC_NO External document number

SAP_DOC_NO Document number of invoice document

FISCAL_YEAR Fiscal year

BVORG Number of cross-company code posting transactions

REVERSAL_DOC Reverse document number

REV_DOC_YEAR Reverse document fiscal year

VENDOR_NAME_EXT External vendor name

POSTAGE_AMOUNT Postal charge

INSURANCE_AMOUNT Insurance amount

FREIGHT_AMOUNT Freight costs

PACKAGE_AMOUNT Packing costs

SGTXT Item text

BVTYP Partner bank type

HBKID Short key for house bank


54

E_STR_HEADER HEADER

SCBANK_IND State central bank indicator

SUPCOUNTRY Supplying country

SUPCOUNTRY_ISO Supplier country ISO code

BLLSRV_IND Service indicator (foreign payment)

KURSF Exchange rate

KURSR Hedged exchange rate

GBETR Hedged amount in foreign currency

TBTKZ Indicator: Subsequent debit/credit

SHEET_NO Entry sheet number

ALLOC_NMBR Assignment number

LFSNR Number of external delivery notes

DSCT_AMOUNT Cash discount amount in document currency

BUS_AREA Business area

WWERT Translation date

PMNT_BLOCK Payment block key

FOLLOW_UP Follow-up flag ID (not available since PD AP 7.2)

NETDT Due date for net payment

NETDT1 Due date day 1

NETDT2 Due date days 2

AUGDT Clearing date

AUGCP Clearing entry date

AUGBL Document number of clearing document

AMOUNT_SPLIT Document posted using invoice split

SKFBT1 Discount amount for discount day/rate 1

SKFBT2 Discount amount for discount days/rate 2


55

E_STR_HEADER HEADER

SKGAINED Gained discount amount

SKLOST Lost discount amount

REP_EXTRACT REPORTER data export carried out

VATDATE Tax reporting date

PAYMT_REF Payment reference

PMTMTHSUPL Payment method supplement

INV_REF_NO Number of the invoice the transaction belongs to

INV_YEAR Fiscal year of relevant invoice (for credit memo)

EC_ARC_ID Content repository identification

EC_DBC_ID SAP ArchiveLink: Document ID

EC_ARC_OBJ Document type

TTIME Processing time by PD AP

TEWCTIME Processing time in workflow

CHECK_TYPE Validation type for additional checks in PROCESS DIRECTOR

PAYR_HBKID Short key for house bank

PAYR_HKTID ID for account details

PAYR_CHECT Check number

BUPLA Business place

J_1BNFTYPE Nota fiscal type

J_1BDOCNUM Document number

J_1BREGIO Region of NF-e issuer

J_1BYEAR Year of NF-e posting date

J_1BMONTH Month of NF-e posting date

J_1BSTCD1 CNPJ number of NF-e issuer

J_1BMODEL Model of nota fiscal


56

E_STR_HEADER HEADER

J_1BDOCNUM9 NF-e: Random number

J_1BCHECKDIGIT Check digit for NF-e access key

J_1BNFEAUTHCODE NF-e: Protocol number

J_1BPREFNO Service NF-e number provided by prefecture

J_1BCHECOD Checking code of Service NF-e

J_1BNFEXMLVER NF-e: XML version

ESRNR POR subscriber number

ESRPZ POR check digit

ESRRE POR reference number

VENDOR_NAME1 Business partner name

VENDOR_NAME2 Business partner name

VENDOR_CITY City

VENDOR_STREET House number and street

CR_DATE Date on which record was created

CR_TIME Time at which record was created

HD_OFFICE Head office account number

HD_OFFICE_DESCR Head office description

COMP_CODE_DESCR Company code description

BUS_AREA_DESCR Business area description

DIFF_INV_DESCR Description of alternative invoicing party

GROSS_AMT_DISP Gross amount in PD AP (negative values)

NET_AMT_DISP Net amount in PD AP (negative values)

CR_USER Processor of PROCESS DIRECTOR document

CR_TIMESTAMP UTC time stamp in long form (YYYYMMDDhhmmss,mmmuuun)

CH_USER Last person to change a record in PROCESS DIRECTOR


57

E_STR_HEADER HEADER

CH_TIMESTAMP UTC time stamp in long form (YYYYMMDDhhmmss,mmmuuun)

CI_COCKPIT_HDR All fields in include, CI_COCKPIT_HDR

E_TAB_ITEM ITEM


INVOICE_ITEM Document item in invoice document


PO_ITEM Item number of purchasing document

REF_DOC Document number of reference document

REF_DOC_YEAR Fiscal year of current period

REF_DOC_IT Item of reference document

ITEM_AMOUNT PROCESS DIRECTOR net amount


QUANTITY Quantity

PO_UNIT Order unit

MATERIAL Material number

ITEM_TEXT Item text



LFSNR Number of external delivery note

DISTRIB Distribution code for multiple account assignment

COND_TYPE Condition type

COND_ST_NO Step number

COND_COUNT Condition counter

FINAL_INV Final invoice indicator


58

E_TAB_ITEM ITEM

RETPO Item return

PART_INV Partial invoice indicator

PACKNO Package number of service

INTROW Line number of service

DA_QUANTITY Quantity

DA_AMOUNT PROCESS DIRECTOR net amount

TAX_CODE Tax code

TAX_RATE Tax rate

TAX_AMOUNT Tax amount in document currency

TAXJURCODE Jurisdiction for tax calculation - tax jurisdiction code

APPROVED Line item/account assignment approved

APPROVER Approver ID

APPROVER_TYPE Approver type

APPROVAL_STATUS Line item/account assignment approved - display only

CURRENT_APPROVER Current item processor

CURRENT_APPROVER_TYPE Current item processor type

NEXT_PROC Next item processor

NEXT_PROC_TYPE Next item processor type

Table name DDIC table name of data table

MATERIAL_TEXT Material description

FOLLOW_UP_ICON Follow-up flag

CI_COCKPIT_ITEM All fields in include, CI_COCKPIT_ITEM


59

E_TAB_TAX TAX


TAX_CODE Tax code

TAX_RATE Tax rate



SHKZG Debit/credit indicator

XEXTN_TXP Indicator: External tax calculation

CI_COCKPIT_TAX All fields in include, CI_COCKPIT_TAX

E_TAB_ACCOUNT ACCOUNT



NET_AMOUNT PROCESS DIRECTOR net amount


TEXT Item text



BSCHL Posting key

COSTCENTER Cost center

ORDERID Order number

WBS_ELEMENT Work Breakdown Structure Element (WBS Element)

SALES_ORD Sales order number

S_ORD_ITEM Item number of SD document

COST_OBJ Cost object

CO_BUSPROC Receiver business process


60


NETWORK Network number for account assignment

NETWORK_OP Network activity

CO_MATERIAL Receiving material

PLANT Plant for receiving material

PROFIT_CTR Profit center



TAX_CODE Tax code

TAX_RATE Tax rate



REC_STATUS Check box

IDOC_NUMBER IDoc number

IDOC_GUID Unique document identification













61


PAOBJNR Profitability segment number (CO-PA)

PASUBNR Profitability segment changes (CO-PA)

COPA_ICON PROCESS DIRECTOR document profile

TR_ACTIVITY Trip activities

TR_NETAMOUNT PROCESS DIRECTOR net amount

TR_CURRENCY Currency key

TR_AMOUNT_TR Travel expenses

TR_DATE Document date in document

TR_TEXT_OLD Item text

APPROVED Line item/account assignment approved

APPROVER Approver ID

APPROVER_TYPE Approver type

APPROVAL_STATUS Line item/account assignment approved - display only

CURRENT_APPROVER Current item processor

CURRENT_APPROVER_TYPE Current item processor type

NEXT_PROC Next item processor

NEXT_PROC_TYPE Next item processor type

GL_ACCOUNT_TEXT G/L account short text

CI_COCKPIT_ACCT All fields in include, CI_COCKPIT_ACCT


62

E_TAB_ACCT_ASSIGN not implemented

CLIENT Client


VERSION Version of PD AP data record

POS_NO Item number



SUBPOS Subitem

SERIAL_NO Sequential number of account assignment

QUANTITY Quantity

ITEM_AMOUNT PROCESS DIRECTOR net amount











ASSET_NO Main asset number

SUB_NUMBER Asset sub-number


CO_AREA Controlling area

CI_COCKPIT_ACCAS All fields in include, CI_COCKPIT_ACCAS


63

The data for PROCESS DIRECTOR AP documents is retrieved by the /COCKPIT/WC_DB_WEBCYCLE_GET function module.

ES_TWC HEADER

CLIENT Client


WC_NO Workflow number

WC_VERSION Version of workflow data

VERSION Version of PD AP data record

DOC_STATUS Document status

WC_ID Workflow ID

WC_DUEDATE Workflow due date

WC_STATUS Workflow status

WC_POS Workflow step position

WC_CH_TIMESTAMP UTC time stamp in long form (YYYYMMDDhhmmss,mmmuuun)

ARCHIVED Check box

WC_INITIATOR Last person to change a record in PROCESS DIRECTOR

Incoming invoice The data for incoming invoices is transferred to PROCESS DIRECTOR Accounts Payable by the /COCKPIT/RFC_DATA_SUBMIT function module.

HEADER I_STR_HEADER




DOC_TYPE Document type





64

HEADER I_STR_HEADER


PSTNG_DATE Posting date in document



GL_ACCOUNT General ledger account

CURRENCY_ISO ISO currency code

CURRENCY_SAP Currency key

GROSS_AMOUNT Amount in document currency

NET_AMOUNT Amount in document currency


BLINE_DATE Baseline date for due date calculation

DSCT_DAYS1 Cash discount day 1

DSCT_DAYS2 Cash discount days 2

NETTERMS Net payment terms period



PYMT_METH Payment method


DEL_COSTS Unplanned delivery costs

DEL_COSTS_TAXC Tax code for delivery costs

EXT_DOC_NO External document number

SAP_DOC_NO Document number of invoice document

USERNAME User name

VENDOR_NAME_EXT External vendor name

POSTAGE_AMOUNT Unplanned delivery costs


65

HEADER I_STR_HEADER

INSURANCE_AMOUNT Unplanned delivery costs

FREIGHT_AMOUNT Unplanned delivery costs

PACKAGE_AMOUNT Unplanned delivery costs

TOLL_AMOUNT Unplanned delivery costs

SGTXT Item text

BVTYP Partner bank type

HBKID Short key for house bank

SCBANK_IND State central bank indicator

SUPCOUNTRY Supplier country

SUPCOUNTRY_ISO Supplier country ISO code

BLLSRV_IND Service indicator (foreign payment)

KURSF Exchange rate

KURSR Hedged exchange rate

GBETR Amount in document currency





DSCT_AMOUNT Cash discount amount in local currency


PMNT_BLOCK Payment block key

VATDATE Tax reporting date

PAYMT_REF Payment reference

PMTMTHSUPL Payment method supplement

FISCAL_YEAR Fiscal year


66

HEADER I_STR_HEADER

WWERT Translation date

EC_ARC_ID Content repository identification

EC_DBC_ID SAP ArchiveLink: Document ID

EC_ARC_OBJ Document type

BUPLA Business place

J_1BNFTYPE Nota fiscal type

J_1BDOCNUM Document number

J_1BREGIO Region of NF-e issuer

J_1BYEAR Year of NF-e posting date

J_1BMONTH Month of NF-e posting date

J_1BSTCD1 CNPJ number of NF-e issuer

J_1BMODEL Model of nota fiscal

J_1BDOCNUM9 NF-e: Random number

J_1BCHECKDIGIT Check digit for NF-e access key

J_1BNFEAUTHCODE NF-e: Protocol number

J_1BPREFNO Service NF-e number provided by prefecture

J_1BCHECOD Checking code of Service NF-e

J_1BNFEXMLVER NF-e: XML version

CI_COCKPIT_HDR All fields in include, CI_COCKPIT_HDR

ITEM I_TAB_ITEM

INVOICE_ITEM Document item in invoice document

PO_NUMBER Purchase order number


REF_DOC Document number of reference document


67

ITEM I_TAB_ITEM

REF_DOC_YEAR Fiscal year of current period

REF_DOC_IT Item of reference document


TAX_CODE Tax code

TAX_RATE Tax rate



ITEM_AMOUNT Amount in document currency


QUANTITY Quantity

PO_UNIT_ISO ISO code for PO unit of measure

PO_UNIT_SAP Order unit


ITEM_TEXT Item text



COND_TYPE Condition type

CI_COCKPIT_ITEM All fields in include, CI_COCKPIT_ITEM

TAX I_TAB_TAX

TAX_CODE Tax on sales/purchases code

TAX_RATE Tax rate



CI_COCKPIT_TAX All fields in include, CI_COCKPIT_TAX


68

ACCOUNT I_TAB_ACCOUNT


NET_AMOUNT Amount in document currency


TEXT Item text

HEADER_DATA Check box



BSCHL Posting key







CO_BUSPROC Receiver business process



CO_MATERIAL Receiving material

PLANT Plant for receiving material





TAX_RATE Tax rate


69

ACCOUNT I_TAB_ACCOUNT



REC_STATUS Check box

IDOC_NUMBER IDoc number

IDOC_GUID Unique document identification












CI_COCKPIT_ACCT All fields in include, CI_COCKPIT_ACCT

Purchase order The data for PROCESS DIRECTOR Accounts Payable documents is retrieved by the BAPI_PO_GETDETAIL function module.

PO_HEADER HEADER


CO_CODE Company code

DOC_CAT Purchasing document category

DOC_TYPE Purchasing document type


70

PO_HEADER HEADER

CNTRL_IND Control indicator for purchasing document type

DELETE_IND Deletion indicator in purchasing document

STATUS Status of purchasing document

CREATED_ON Date on which record was created

CREATED_BY Person who created the object

ITEM_INTVL Item number interval

LAST_ITEM Last item number

VENDOR Vendor's account number

LANGUAGE Language key


DSCNT1_TO Cash discount day 1

DSCNT2_TO Cash discount days 2

DSCNT3_TO Cash discount days 3

CASH_DISC1 Cash discount percentage 1

CASH_DISC2 Cash discount percentage 2

PURCH_ORG Purchasing organization

PUR_GROUP Purchasing group


EXCH_RATE Direct quoted exchange rate

EX_RATE_FX Indicator: Fixing of exchange rate

DOC_DATE Purchasing document date

VPER_START Start of validity period

VPER_END End of validity period

APPLIC_BY Closing date for applications

QUOT_DEAD Deadline for submission of bid/quotation


71

PO_HEADER HEADER

BINDG_PER Binding period for quotation

WARRANTY Warranty date

BIDINV_NO Bid invitation number

QUOTATION Quotation number

QUOT_DATE Quotation submission date

REF_1 Customer's or vendor's internal reference

SALES_PERS Responsible salesperson in vendor's office

TELEPHONE Vendor's telephone number

SUPPL_VEND Supplying vendor

CUSTOMER Customer number

AGREEMENT Number of principal purchasing agreement

REJ_REASON Reason for rejection of quotations and sales orders

COMPL_DLV Complete delivery stipulated for each purchase order

GR_MESSAGE Indicator: Goods receipt message

SUPPL_PLNT Supplying (issuing) plant in case of stock transport order

RCVG_VEND Field not used

INCOTERMS1 Incoterms (part 1)


TARGET_VAL Cumulative planned value

COLL_NO Collective number

DOC_COND Number of the document condition

PROCEDURE Procedure (pricing, output control, acct. det., costing, etc.)

UPDATE_GRP Update group for statistics update


EXPORT_NO Number of foreign trade data in MM and SD documents


72

PO_HEADER HEADER

OUR_REF Our reference

LOGSYSTEM Logical system

SUBITEMINT Item interval for sub-items

MAST_COND Document with time-dependent conditions

REL_GROUP Release group

REL_STRAT Release strategy

REL_IND Release indicator: Purchasing document

REL_STATUS Release status

SUBJ_TO_R Release not yet completely in effect

TAXR_CNTRY Country for tax return

SCHED_IND Indicator for scheduling agreement release documentation

VEND_NAME Name 1

CURRENCY_ISO ISO currency code

EXCH_RATE_CM Indirect quoted exchange rate

HOLD Purchase order not yet complete

PO_HEADER_TEXTS HEADER_TEXTS

TEXT_LINE Text line

PO_ITEMS ITEM




STATUS RFQ status

CHANGED_ON Purchasing document item change date


73

PO_ITEMS ITEM

SHORT_TEXT Short text


PUR_MAT Material number

CO_CODE Company code

PLANT Plant

STORE_LOC Storage location

TRACKINGNO Requirement tracking number

MAT_GRP Material group

INFO_REC Number of purchasing information record

VEND_MAT Material number used by vendor

TARGET_QTY Target quantity

QUANTITY Purchase order quantity

UNIT Order unit

ORDERPR_UN Order price unit (purchasing)

CONV_NUM1 Numerator for conversion of order price unit to order unit

CONV_DEN1 Denominator for conversion of order price unit to order unit

CONV_NUM2 Numerator for conversion of order unit to base unit

CONV_DEN2 Denominator for conversion of order unit to base unit

NET_PRICE Net price in purchasing document (in document currency)

PRICE_UNIT Price unit

NET_VALUE Net order value in PO currency

GROS_VALUE Gross order value in PO currency

QUOT_DEAD Deadline for submission of bid/quotation

GR_PR_TIME Goods receipt processing time in days



74

PO_ITEMS ITEM

SETT_GRP1 Settlement group 1 (Purchasing)

QUAL_INSP Stock type

INFO_UPD Indicator: Update information record

PRNT_PRICE Print price

EST_PRICE Estimated price indicator

NUM_REMIND Number of reminders or urging messages (expeditors)

REMINDER1 Number of days until first reminder/urging letter (expeditor)

REMINDER2 Number of days until second reminder/urging letter (expeditor)

REMINDER3 Number of days until third reminder/urging letter (expeditor)

OVERDELTOL Overdelivery tolerance limit

UNLIMITED Indicator: Unlimited overdelivery allowed

UNDER_TOL Underdelivery tolerance limit

VAL_TYPE Valuation type

VAL_CAT Valuation category

REJ_IND Rejection indicator

COMMENT Internal comment on quotation

DEL_COMPL "Delivery completed" indicator


ITEM_CAT Item category in purchasing document

ACCTASSCAT Account assignment category

CONSUMPT Consumption posting

DISTRIB Distribution indicator for multiple account assignment

PART_INV Partial invoice indicator

GR_IND Goods receipt indicator

GR_NON_VAL Goods receipt, non-valuated


75

PO_ITEMS ITEM

IR_IND Invoice receipt indicator

GR_BASEDIV Indicator: GR-based invoice verification

ACKN_REQD Order acknowledgment requirement

ACKNOWL_NO Order acknowledgment number

AGREEMENT Number of principal purchasing agreement

AGMT_ITEM Item number of principal purchasing agreement

RECON_DATE Reconciliation date for agreed cumulative quantity

AGRCUMQTY Agreed cumulative quantity

FIRM_ZONE Firm zone (go-ahead for production)

TRADE_OFF Trade-off zone (go-ahead for material procurement)

BOM_EXPL Indicator: BOM explosion

EXCLUSION Exclusion in outline agreement item with material class

BASE_UNIT Base unit of measure

SHIPPING Shipping instructions

OUTL_TARGV Target value for outline agreement in document currency

NOND_ITAX Non-deductible input tax

RELORD_QTY Standard release order quantity

PRICE_DATE Date of price determination

DOC_CAT Purchasing document category

EFF_VALUE Effective value of item

COMMITMENT Item affects commitments

CUSTOMER Customer

ADDRESS Address

COND_GROUP Condition group for vendor

NO_C_DISC No cash discount granted on this item


76

PO_ITEMS ITEM

UPDATE_GRP Update group for statistics update

PLAN_DEL Planned delivery time in days

NET_WEIGHT Net weight

WEIGHTUNIT Unit of weight

TAX_JUR_CD Jurisdiction for tax calculation - tax jurisdiction code

PRINT_REL Indicator: Print-relevant schedule lines exist

SPEC_STOCK Special stock indicator

SETRESERNO Settlement reservation number

SETTLITMNO Item number of settlement reservation

NOT_CHGBL Quality inspection indicator cannot be changed

CTR_KEY_QM Control key for quality management in procurement

CERT_TYPE Certificate type

EAN_UPC International article number (EAN/UPC)

CONF_CTRL Confirmation control key

REV_LEV Revision level

FUND Fund

FUNDS_CTR Funds center

CMMT_ITEM Commitment item

BA_PARTNER Business area reported to partner

PTR_ASS_BA Assumed business area of business partner


PARTNER_PC Partner profit center

PRICE_CTR Pricing date category (controls date of price determination)

GROSS_WGHT Gross weight

VOLUME Volume


77

PO_ITEMS ITEM

VOLUMEUNIT Volume unit



ADVANCE Advance procurement: Project stock

PRIOR_VEND Prior vendor

SUB_RANGE Vendor sub-range

PCKG_NO Package number

STATISTIC Item is statistical

HL_ITEM Higher-level item in purchasing documents

GR_TO_DATE Latest possible goods receipt

SUPPL_VEND Vendor to be supplied/who is to receive delivery

SC_VENDOR Subcontracting vendor

CONF_MATL Cross-plant configurable material

MAT_CAT Material category

KANBAN_IND Kanban indicator

ADDRESS2 Number of delivery address

INT_OBJ_NO Configuration (internal object number)

ERS Evaluated Receipt Settlement (ERS)

GRSETTFROM Start date for GR-based settlement

LAST_TRANS Last transmission

TRANS_TIME Time

SER_NO Sequential number

PROMOTION Promotion

ALLOC_TBL Allocation table number

AT_ITEM Item number of allocation table


78

PO_ITEMS ITEM

POINTS Number of points

POINTS_UN Points unit

SEASON_TY Season category

SEASON_YR Season year

SETT_GRP_2 Settlement group 2 (rebate settlement, purchasing)

SETT_GRP_3 Settlement group 3 (rebate settlement, purchasing)

SETT_ITEM Item relevant to subsequent (period-end rebate) settlement

ML_AKT Material ledger activated at material level

REMSHLIFE Minimum remaining shelf life

RFQ RFQ number

RFQ_ITEM Item number of RFQ

CONFIG_ORG Origin of configuration

QUOTAUSAGE Quota arrangement usage

SPSTCK_PHY Special stock indicator for physical stock transfer

PREQ_NO Purchase requisition number

PREQ_ITEM Item number of purchase requisition

MAT_TYPE Material type

SI_CAT Sub-item category, purchasing document

SUB_ITEMS Sub-items exist

SUBTOTAL_1 Condition subtotal 1 from calculation schema







79

PO_ITEMS ITEM

SUBITM_KEY Processing key for sub-items

MAX_CMG Maximum cumulative materials go-ahead quantity

MAX_CPGO Maximum cumulative production go-ahead quantity

RET_ITEM Return item

AT_RELEV Relevant to allocation table

ORD_REAS Reason for ordering

DEL_TYP_RT Delivery type for returns to vendors

PRDTE_CTRL Material freight group

MANUF_PROF Manufacturer part profile

MANU_MAT Manufacturer part number

MFR_NO Manufacturer number

MFR_NO_EXT External manufacturer code name or number

ITEM_CAT_EXT Item category in purchasing document

PO_UNIT_ISO Order unit in ISO code

ORDERPR_UN_ISO ISO code for purchase order price unit

BASE_UOM_ISO Base unit of measure in ISO code

WEIGHTUNIT_ISO ISO code for unit of weight

VOLUMEUNIT_ISO Volume unit in ISO code

POINTS_UN_ISO ISO code for points unit

CONF_MATL_EXTERNAL Long material number (future development) for CONF_ field

CONF_MATL_GUID External GUID (future development) for CONF_MATL field

CONF_MATL_VERSION Version number (future development) for CONF_MATL field

MATERIAL_EXTERNAL Long material number (future development) for MATERIAL field

MATERIAL_GUID External GUID (future development) for MATERIAL field

MATERIAL_VERSION Version number (future development) for MATERIAL field


80

PO_ITEMS ITEM

PUR_MAT_EXTERNAL Long material number (future development) for PUR_M field

PUR_MAT_GUID External GUID (future development) for PUR_MAT field

PUR_MAT_VERSION Version number (future development) for PUR_MAT field

Inner document - PO flip The data for PROCESS DIRECTOR Accounts Payable documents is retrieved by the BAPI_PO_GETDETAIL function module.

PO_ITEMS inner document




SHORT_TEXT Short text


QUANTITY Purchase order quantity

UNIT Order unit

ORDERPR_UN Order price unit (purchasing)

CONV_NUM1 Numerator for conversion of order price unit to order unit

CONV_DEN1 Denominator for conversion of order price unit to order unit

CONV_NUM2 Numerator for conversion of order unit to base unit

CONV_DEN2 Denominator for conversion of order unit to base unit

NET_PRICE Net price in purchasing document (in document currency)

PRICE_UNIT Price unit


OVERDELTOL Overdelivery tolerance limit

UNLIMITED Indicator: Unlimited overdelivery allowed

UNDER_TOL Underdelivery tolerance limit


81

PO_ITEMS inner document


ITEM_CAT Item category in purchasing document

PO_ITEM_HISTORY_TOTALS inner document

DELIV_QTY Quantity of goods received

IV_QTY Quantity invoiced

Data retrieved from the V_LIMIT table:

V_LIMIT inner document

SUMLIMIT Overall limit

SUMNOLIM No limit

COMMITMENT Expected value of overall limit

ACTVALUE Total value of unplanned entered services

Vendor master data The data for PROCESS DIRECTOR Accounts Payable documents is retrieved by the BAPI_VENDOR_GETDETAIL function module.

GENERALDETAIL HEADER

VENDOR Account number of vendor or creditor

NAME Name 1

NAME_2 Name 2

NAME_3 Name 3

NAME_4 Name 4

CITY City

DISTRICT District

PO_BOX P.O. box

POBX_PCD P.O. box postal code


82

GENERALDETAIL HEADER

POSTL_CODE Postal code

REGION Region (state, province, county)

STREET House number and street

COUNTRY Country key

COUNTRYISO Country ISO code

POBX_CTY PO box of city

LANGU Language key

LANGU_ISO Language according to ISO 639

BAPIVENDOR_04 All fields from append, BAPIVENDOR_04

BANKDETAIL BANKDETAIL


BANK_CTRY Bank country key

BANK_KEY Bank key

BANK_ACCT Bank account number

CTRL_KEY Bank control key

PARTNER_BK Partner bank type

COLL_AUTH Indicator: Is there collection authorization?

BANK_REF Reference specifications for bank details

BAPIVENDOR_06_APPEND All fields from append, BAPIVENDOR_06_APPEND

Data retrieved from the LFA1 table:

Table LFA1 HEADER

LOEVM Central deletion flag for master record

SPERR Central posting block


83

Data retrieved from the TIBAN table:

Table LFA1 HEADER

IBAN IBAN (International Bank Account Number)

The data for PROCESS DIRECTOR Accounts Payable documents is retrieved by the BAPI_VENDOR_GETDETAIL function module.

Table COMPANYDETAIL COMPANYDETAIL



CLERK Accounting clerk

HD_OFFICE Head office account number

ALT_PAYEE Account number of alternative payee

CUVD_CLEAR Indicator: Clearing between customer and vendor


ACT_AT_VEN Our account number with vendor

VEND_USER Clerk at vendor

INTERNET Internet address of partner company clerk

FAX Accounting clerk's fax number at the customer/vendor

BAPIVENDOR_05 All fields from append, BAPIVENDOR_05

Data retrieved from the LFB table:

Table LFB1 COMPANYDETAIL

LOEVM Central deletion flag for master record

SPERR Central posting block

Data retrieved from the LFAS table:

Table LFAS VAT_NUMBER

LAND1 Country key

STCEG VAT registration number


84

Data retrieved from the WYT3 table:

Table WYT3 BUS_PARTNER

LIFN2 Reference to other vendor

ReadSoft Supplier Portal · application server; for example, a war file for Apache Tomcat. Some of...

Documents

Transcript of ReadSoft Supplier Portal · application server; for example, a war file for Apache Tomcat. Some of...