Steps to Export / Import a PSE via

STRUST

Posted by ITsiti — February 2, 2016 in SAP Basis — Leave a reply

Symptom

You are executing a system refresh and wanted to retain the PSE file in the
STRUST.

Solution

EXPORT PSE FROM STRUST

1. Execute transaction code STRUST. As an example, you want to export
SYSTEM PSE file. Double click and go to PSE > Export. A dialog box will
prompt to save the export PSE file.

IMPORT PSE TO STRUST

1. In transaction code STRUST. Click on File and from the dialog box
prompted, locate your previous saved PSE file. You will see the PSE details
on the right panel side.

2. Once verified, go to PSE > Save As to apply the PSE.

Reference

SAP Note 1473710 – STRUST: How to Export/Import a PSE from/to STRUST

SAP Blog

Using ABAP with the SAP API Business Hub

1
2
3
4
5
6


Join the conversation on Facebook

o Share this page

o Follow SAP Developers

Join the conversation on Twitter

o Share this page

o Follow SAP Developers

Subscribe to the YouTube Channel

o Subscribe to SAP Developers

Join the conversation on LinkedIn

o Share this page

o Follow SAP Developers

View our projects on GitHub

o View our projects

Share via email

o Share this page

 Details
Code Snippets
// Explore More Tutorials

Using ABAP with the SAP API Business Hub

Meredith Hassett

12/02/2018

Beginner
15 min.
ABAP Development, Tutorial, Beginner
Add a code snippet from the API Hub into your ABAP report.
You will learn

In this tutorial, you will learn how to use the pre-generated code from the SAP API Business
Hub in an ABAP report. You will need to have configured your ABAP system to make an
HTTP request.

 Step 1: Configure your ABAP Proxy

 Step 2: Get your SSL Certificate
 Step 3: Add your certificate to ABAP
 Step 4: Create the ABAP program report
 Step 5: Get the ABAP code from API Business Hub
 Step 6: Add API call and run from ABAP
 Back to Top

Prerequisites
 ABAP system should be configured to call http APIs
 Testing API Business Hub APIs with Curl

Configuring the proxy settings is not a required step for all systems. Verify that your system
needs to have the proxy configured before completing steps 1 through 3.

Step 1: Configure your ABAP Proxy

From the SAP Logon pad, launch the SAP Logon screen.
Enter the login credentials in R/3 ABAP System.
Configure your proxy settings by going to transaction SICF and clicking on Execute.
Open Proxy settings page by pressing Ctrl + F2 and set the proxy.
Done

Log on to answer question

Step 2: Get your SSL Certificate

In Google Chrome, export SSL certification.

To get to the SSL certificate, enter F12, go to Security tab, click on View Certificate, click on
Details, and select Copy to File. From here, you can export the certificate by path.
Done

Log on to answer question

Step 3: Add your certificate to ABAP

Once you export the certificate by path, you will need to import it into your ABAP system.
To import the certificate in your ABAP system, go to the transaction STRUST, open SSL
client SSL Client (Standard), and switch to Edit mode.
Click on Import Certificate. Select the certificate you exported from Google Chrome in the
previous step. Click Add to Certificate List and save.
In order to reflect your new SSL settings, you will need to restart your ICM. To restart the
ICM, go to the transaction SMICM. Navigate to Administration > ICM > Exit Hard > Global.
The ICM restart message will appear. Select Yes.

Restart the ICM processes. Make sure no client is communicating during restart.
Done

Log on to answer question

Step 4: Create the ABAP program report

In your ABAP system, go to the transaction se38.

Create a new report. Enter the program name, such as ZAPI_HUB_TEST, select Source Code,
and click Create.
Provide the following details on the Program Attributes screen.

Field Name Value

Title testing API
Type Executable program
OPTIONAL: Status Test Program

Save, Activate, and Execute the report.

Done

Log on to answer question

Step 5: Get the ABAP code from API Business Hub

To get the ABAP code snippets that are available in the SAP API Business Hub, go to the SAP
API Business Hub, which can be found at api.sap.com, from your browser. Navigate to the
API packages page and find the SAP Translation Hub API.
Click the Expand Operations link on the Domains API. Click Generate Code on the GET
/domains method.
Click on the tab for ABAP from available languages and click Copy to Clipboard.
 5

Paste in the copied ABAP code from the API Hub in the text box below.

Submit Answer
×
Log on to answer question
Step 6: Add API call and run from ABAP

Back in your ABAP system, paste the code snippet into the report.
Replace the <API_KEY> with your API key value. This is also available in the SAP API Business
Hub and is specific to your user and app. Save, Activate, and Execute the report.
 If you see a message returned with data, and not an error, you have successfully tested a
call to an API from the SAP API Business Hub.

Digital Invoicing configuration for Mexico

configuration in SAP SD
Skip to end of metadata

 Created by Former Member on Sep 26, 2014

Go to start of metadata

1.1 Purpose of the Document

This document outlines the customization settings that are to be done pertaining to SD to implement Digital Invoicing for
Mexico. The Mexican tax regulations have made the implementation of electronic invoices by domestic business
entities, mandatory. A digital/electronic invoice (Factura Electrónica), also called a digital tax receipt, e-invoice or
efactura is an electronic document that meets the legal and statutory requirements similar to that of pre-printed invoices.
The Electronic invoicing process requires digital certificates and a series of folio numbers obtained from the government
in order to generate the electronic invoice in the SAP system. The various settings with respect to SD configuration that
SAP recommends in order to set up the electronic invoicing process is outlined in this document. The complete setup of
the Digital Invoicing process in SAP however is a combination of various tasks to be performed such as implementation
of recommended notes, development activities involving creation of smartforms, BADI changes; storing of Digital
certificates etc.

1.2 Scope of the document

This document describes only the configuration steps with respect to SD that need to be completed in order to setup
the Digital Invoice functionality for Mexico.

1.3 Prerequisites
SAP recommends the implementation of the following Notes before the customization for SD is done as these are
dependent activities. The below table gives the list of Notes to be implemented.
The latest Support Package needs to be implemented in order that the following nodes of the customizing activities
become available as per the screenshot below.
The Digital Signature Settings node will reveal the following Customizing activities:

If the latest support package has not been implemented, the following configuration settings can be maintained by calling
up the corresponding views manually in transaction SM30.
 1.4 Configuration Settings
Official Document No. Configuration
1.4.1 Maintain document class
View : V_DOCCLS
Document classes are used to distinguish among the different types of official documents as prescribed by the
authorities, for example, invoices, debit memos, credit memos, or delivery notes.

Go to SM30 and enter the view name V_DOCCLS.

1.4.2 Assign document classes to document types
View: V_T003_B_I.

In this step the document classes defined in the previous step are assigned to the accounting document types that are
being used in the current business scenario.
1.4.3 Maintain Number Groups for Folio Numbers
View : V_1ANUMGR1

Each business entity needs to get the Folio numbers (no. range) from the Mexican government. A no. group needs to
be created at first in order to assign the folio number range to it. Different number ranges can exist for different type of
documents such as Credit memos, Debit Memos, Invoices etc.
1.4.4 Maintain number ranges for Folio Numbers.
T-code : SNRO, Object : J_1AOFFDOC

The number range of the Folio numbers got from the government is maintained in this step.
1.4.5 Assign number ranges
View : V_OFNUM_MX

The number ranges for the Folio numbers defined in the previous step are assigned to the various Document Classes
(such as Credit memos. Debit memos) defined earlier. This step helps to determine different Number ranges (through
No. range groups defined) for the different type of documents.

Generation of Digital Signature

1.4.6 Assign Legal Tax Abbreviations to Account Keys
View : IDMX_DI_VTAXES

In this step the abbreviation for the various taxes used in the business scenario are defined.
Example

Assume that you record the special tax on goods and services (Impuesto Especial sobre Producción y Servicios in
Spanish, IEPS) in an account represented by the account key IEP, and value-added tax (Impuesto al Valor Agregado in
Spanish, IVA) in an account represented by the account key MWS. You enter the following combination of account keys
and tax abbreviations:
1.4.7 Definition & Assignment of text IDs to store the data for the Digital Signature
Tcode- VOTXN

In this Customizing activity, you set up the system so that it can save, and later retrieve the results of the digital
signature process. Since not every piece of data required for the digital signature process is stored in a field in the
system, the system uses text fields in the billing document, for example at header level, to store the derived results of
the digital signature process.
Note: Since the text fields contain data related to the digital signature and any manipulation of the data would render the
recipient's view of the digital billing document useless, the text fields are not visible in the invoice. The language of the
text fields in which the system stores data is the language of your company code in the system. In some text fields, to
comply with legal regulations in Mexico, the system always enters texts in Spanish, for example, the document type for
payment flow, regardless of the language of the company code.

The derived results of the digital signature process that the system stores in text fields are grouped in categories:
 Encrypted character string
 The result of applying the signer's private key to the hashed character string. The result represents a unique fingerprint
of the character string, which contains the legally-defined data. The encrypted character string is stored in Base 64
encoded format.
 Document type for payment flow
 Shows whether the document is of type income (ingreso), expense (egreso), or transfer (traslado). The system always
enters the text in Spanish, for example, ingreso.
 Approval year for official document number
 Approval number for official document number
 Serial number of certificate
 The serial number of the certificate that you receive from the authorities to sign electronic billing documents digitally.
 Payment installment texts
 Contains the number of installments in which a payment is divided and the corresponding legally-defined text in
Spanish. The installments data is stored in the Customizing activity Define Terms of Payment.
 Document header supplement (complemento)
 Supplemental data that some companies must provide at header level in billing documents.
 Line item supplement (complemento)
 Supplemental data that some companies must provide at line item level in billing documents.
 MD5 hashed character string
 The result of applying the hash algorithm, MD5, to the original input message.

The hashed character string is stored in hexadecimal encoded format.

 Original input message
 The complete set of data in the billing document and derived data required by Mexican law for signing billing documents
digitally. The original input message is stored as a character string.
 Addendum (addenda)

 Contains additional data that customers can choose to include in their billing documents.

1.4.8 Determine Text IDs to Store Billing Document Data

View - IDMX_DI_VTXTID

Creation of Output type for triggering the Digital Invoice

1.4.9 Create Output Type
T-code – NACE

A new output type (ZMDI) is created and the program that generates the digital invoice in pdf & xml formats and
smartform are assigned to this output type.

Both ‘print output’ and ‘external send’ are configured so that the output can be printed as well as sent as an email to the
email ids that are maintained in the customer master.
1.4.10 Assignment of output type to Output Determination procedure
T-code – NACZ
1.4.11 Maintain Output condition records
T-code – VV31

This step is done in order to determine the output type automatically during billing. Based on the conditions (access
sequence) during which the o/p needs to get triggered – Eg: Based on Sales org / Billing type , maintain the condition
records and save.

1.5 Additional Notes

For further Information the following Notes can be referred
 1280467 FAQ Digital Invoice Mexico
 1301160 ODN enabled in SD and FI for Mexico for digital invoicing
 1300880 Digital Invoice Mexico: Import Certificates
 1303712 Mexico: Enable Creation of Digital Signature in SD
 1296042 XML file Digital Invoice Mexico

Analytics for SAP TCode SIGNA

Register Signature Application
SIGNA Analytics

 Network Layout
 Tree Layout

SIGNA Analytics Data

Called TCode

SM30 (Call View Maintenance)

6828

Package

DS (Digital Signature)

14

Parant Package

ABA_TECH (NW ABA: Main Package)

55

Application Component

CA-DSG (Digital Signature)

17

Application Component

CA (Cross-Application Components)

10821

Software Component

SAP_ABA (Cross-Application Component)

2192

SIGNA Analytics - Called TCode SM30

10
Show entries
Search:

Top
TCode Description Module Component
Module

Finanzpositionen ->
/SAPF15/FIPO2BW PSM-FM PSM EA-PS
Bewirtschafter

F15 Klärung VSL ->

/SAPF15/TRMBUTYP PSM-FM PSM EA-PS
Buchungstyp

Feldzuordnung SAP ->

/SAPF15/TFLDMAP PSM-FM PSM EA-PS
F15

F15 Klärung
/SAPF15/TRMKFAF PSM-FM PSM EA-PS
Buchungstyp -> KFA

F15 Klärung HKR4

/SAPF15/TRMKFAH4 PSM-FM PSM EA-PS
Fehlercode -> KFA

F15 Klärung ZÜV900

/SAPF15/TRMKFAZ9 PSM-FM PSM EA-PS
Fehlercode -> KFA

NF Rate Reference IS-MP-

/NFM/C_RATEREF IS-MP ECC-DIMP
PurchOrg --> SOrg NF

/AIN/ACTTYPE Action Types AIE-AII AIE AIN

Action Type - Bus. Proc. -

/AIN/ACTTYPEBP AIE-AII AIE AIN
Dev. Role

Assign profile to GTIN

AIE-AII AIE AIN
/AIN/ASGN_PRF_FORMAT and Flt value

Device Event
/AIN/EVENT AIE-AII AIE AIN
Maintenance

/AIN/ID_COMP_PREFIX Maintain Company Prefix AIE-AII AIE AIN

Object Category
/AIN/OBJ_CAT_DET AIE-AII AIE AIN
Determination

Assign Profile for Pack AIE-AII-

AIE AIN
/AIN/PACK_MON_PROFIL Monitor UI

Assign profile to ID and

AIE-AII AIE AIN
/AIN/PRFASGN_ENCTYPE Encod. Type

Assign profile to GTIN

/AIN/PRFASGN_FILTER AIE-AII AIE AIN
and Flt value
 Top
TCode Description Module Component
Module

Assign profile to GTIN

/AIN/PRFASGN_GRAIFLT AIE-AII AIE AIN
and Flt value

Assign profile to GTIN

/AIN/PRFASGN_GTNFLT AIE-AII AIE AIN
and Flt value

Backend Message
/AIN/RULECONDBM AIE-AII AIE AIN
conditions

Fixed Reader Message

/AIN/RULECONDFRM AIE-AII AIE AIN
conditions

Showing 1 to 20 of 500 entries

 Previous
 1
 2
 3
 4
 5
 …
 25
 Next

500 of 6,828 tcodes loaded. We did not load the full list for performance considerations.
You may choose to download the Books or Sheets to get the full list.

SIGNA Analytics - Package DS

Top
TCode Description Module Component
Module

CA-
DSLOG Signature Tool: Log Display CA
DSG SAP_ABA

CA-
ELSIG00 Signature Strategy CA
DSG SAP_ABA

Authorization Grp Digital CA-

ELSIG01 CA
Signatures DSG SAP_ABA

CA-
ELSIG02 Digital Signature CA
DSG SAP_ABA
 Top
TCode Description Module Component
Module

Signature Method for Signat. CA-

ELSIG03 CA
Object DSG SAP_ABA

Signature Method for Signat. CA-

ELSIG03N CA
Object DSG SAP_ABA

CA-
SIGNA Register Signature Application CA
DSG SAP_ABA

CA-
SIGNO Register Signature Object CA
DSG SAP_ABA

CA-
(empty) CA
S_ABA_72000132 DSG SAP_ABA

CA-
(empty) CA
S_ABA_72000133 DSG SAP_ABA

CA-
(empty) CA
S_ABA_72000134 DSG SAP_ABA

CA-
(empty) CA
S_ABA_72000135 DSG SAP_ABA

CA-
(empty) CA
S_ABA_72000136 DSG SAP_ABA

CA-
S_SI3_21000049 (empty) CA
DSG SAP_ABA

SIGNA Analytics - Parant Package ABA_TECH

10
Show entries

Search:

Top
TCode Description Module Component
Module

CA-BFA-
BA10 Subsystem Configuration CA SAP_ABA
TRA

Config. Transceiver / CA-BFA-

BA11 CA SAP_ABA
Upload Files TRA

BC-MID-
BMV0 Manage Data Transfers BC SAP_ABA
ALE-UTI
 Top
TCode Description Module Component
Module

Number Range BC-MID-

BMVN BC SAP_ABA
Maintenance: DI_JOBID ALE-UTI

Service Session SV-SMG-

DSA SV SAP_ABA
Workbench SVD-SWB

DSVAS: ITS start SV-SMG-

DSA_ITS SV SAP_ABA
transaction SVD-SWB

Open the Service SV-SMG-

DSA_SESSION_OPEN SV SAP_ABA
Assistant session SVD-SWB

Service Development SV-SMG-

DSADEV_OLD SV SAP_ABA
Workbench SVD-SWB

Signature Tool: Log

DSLOG CA-DSG CA SAP_ABA
Display

ELSIG00 Signature Strategy CA-DSG CA SAP_ABA

Authorization Grp Digital

ELSIG01 CA-DSG CA SAP_ABA
Signatures

ELSIG02 Digital Signature CA-DSG CA SAP_ABA

Signature Method for

ELSIG03 CA-DSG CA SAP_ABA
Signat. Object

Signature Method for

ELSIG03N CA-DSG CA SAP_ABA
Signat. Object

Maintenance View for CA-EUR-

HOSH CA SAP_ABA
Table ADMI_CRIT CNV

MASS Mass Change CA-GTF-MS CA SAP_ABA

MASSD Mass Maintenance CA-GTF-MS CA SAP_ABA

Maintain Mass
MASSOBJ CA-GTF-MS CA SAP_ABA
Maintenance Objects

Copy System Variant as

MASSS2V CA-GTF-MS CA SAP_ABA
Variant

Copy Variant as System

MASSV2S CA-GTF-MS CA SAP_ABA
Variant

Showing 1 to 20 of 55 entries
  Previous
 1
 2
 3
 Next

SIGNA Global Descriptions

Language Description

中文 登记签字应用程序

Thai แอพพลิเคช ันของลายเซ็นทีรี่ จสิ เตอร ์

한국어 서명어플리케이션 등록

Română Înregistrare aplicaţie pt. semnătură

Slovenščina Registracija aplikacije signature

Hrvatski Registriraj aplikaciju potpisivanja

Українська Реєструвати застосунок підпису

#### ‫التوقيع تطبيق نسجيل‬

‫עברית‬ ‫לחתימה בקשה רישום‬

Čeština Registrace aplikace podpisu

Deutsch Signaturanwendung registrieren

English Register Signature Application

Français Enregistrer application de signature

Ελληνική Καταχώριση Εφαρμογής Υπογραφής

Magyar Aláírási alkalmazás regisztrálása

Italiano Registrare applicazione firme

日本語 署名アプリケーション登録

Dansk Registrer signaturapplikation

polski Rejestracja wykorzystania podpisu

繁體中文 註冊簽名應用程式

Nederlands Handtekeningapplicatie registreren

 Language Description

Norsk Registrer signaturapplikasjon

Português Registrar aplicação de assinatura

Slovenčina Registrácia aplikácie podpisu

Русский Регистрация приложения подписи

Español Registrar aplicación de firma

Türkçe İmza uygulamasını kaydet

Suomi Rekisteröi allekirjoitussovellus

Svenska Registrera signaturapplikation

±êÛÓÐàáÚØ Регистриране приложение на подписи

Català Registrar aplicació signatura

Srpski (Lat.) Registruj aplikaciju potpisivanja