Kontakt

Ansicht
Dokumentation

CRM_WEBREQ_EXTERN_WITH_UPLOADA - Offline Creation of a Web Request with Attachments

CRM_WEBREQ_EXTERN_WITH_UPLOADA - Offline Creation of a Web Request with Attachments

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The program is a sample program for calling the external interface for Web requests with attachments.

You can create a Web request with attachments through the external interface using this program. The XML file for a Web request is imported through an external interface and generates, in the same way as online Web requests over the Internet, a business transaction with which the Web request is linked. The program also supports the upload of files that you wish to include as attachments with the request.

During the program run you are prompted to select the following files one after the other for upload:

  1. Request as XML file matching the request data structure of the selected request category
  2. Attachment 1 (JPG file)
  3. Attachment 2 (any other file, for example, *.doc, *.txt, *.pdf , *.ppt)

Integration

The program uses the framework for Web requests in SAP S/4 HANA for customer management.

Prerequisites

  • The request category must have been created in the system with a related request data structure and transaction type. The parameter for the request category is a required parameter.
  • An XML file "suitable" for the request category must be available for uploading from the local hard disk. This is the first file the program prompts you to specify. The XML tags used in the XML file must also exist in the definition of the request data structure. If the program is called by a Unicode system, the XML file must be converted appropriately beforehand.
  • The business partners for Requester and Creator are optional parameters.
However if they are entered, they must contain the correct business partner numbers. Otherwise the program terminates.
  • A JPG file to be uploaded as an attachment for the business transaction being created must be available on the local hard disk beforehand. This is the second file the system prompts you to specify.
  • Any other file (*.txt, *.ppt, *.doc, *.pdf , *.xml) for uploading as the second attachment must be available on the local hard disk beforehand. This is the third file the program prompts you to specify.

Features

If processing is free of errors, a Web request is created. This means a business transaction with the linked form (XML request data). In addition, the two files included in the upload are created in the document system and a link associating them is saved as an attachment for the generated transaction.

Selection

  • Request category(required entry)
    Valid request category for Web requests
  • Creator(optional entry)
    Business partner creating request
  • Requester(optional entry)
    Person placing request
  • Category(optional entry)
    Web requests created offline and online can be differentiated between in transaction processing using categories.

Standard Variants

Output

If no errors occur during processing, the transaction number and the leading business transaction category of the created business transaction are output. If errors occur during processing, an error message appears.

Activities

For more information, see the documentation for the related function module CRM_WEBREQ_EXTERN_CREATE_DOC.

Example






CPI1466 during Backup   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3962 Date: 20240531 Time: 020435     sap01-206 ( 91 ms )