Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-HMED (Application Component) Clinical System⤷
NMED_DOC (Package) IS-H*MED: Medical Documents
IMG Activity
| ID | ISHMED_COM_DOC_BADI2 | BAdI for Unpacking Received Documents |
| Transaction Code | S_PRI_97000120 | (empty) |
| Created on | 20070111 | |
| Customizing Attributes | ISHMED_COM_DOC_BADI | BAdI for Document Modification (Incoming and Outgoing) |
| Customizing Activity | ISHMED_COM_DOC_BADI2 | BAdI for Unpacking Received Documents |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_COM_DOC_BADI2 |
Use
This BAdI gets a received document transferred. Its task is to prepare the contents and the header data of the document in such a way that this information enables a clinical document to be created.
Requirements
Standard settings
Activities
Create a BAdI implementation for each MIME type for which documents are received and assign the implementation via the filter settings to the appropriate MIME type.
An implementation already exists for receiving documents in i.s.h.med dispatch format for medical documents. The MIME type application/x ishmed meddoc exp+xml is used for these documents.
Implement the BAdI in such a way that it receives the input data and thus fills the changing parameters as follows:
The structure CS_DOCADMIN and the reference CR_DOC_CONTENT must be filled by the BAdI. Fill CS_DOCADMIN with the management data of the document to be created and CR_DOC_CONTENT with the document contents. For CR_DOC_CONTENT please note the class documentation CL_ISHMED_DOC_CONTENT.
The return value CS_DOC_EXTERNAL_HEADER receives further information about the document. Filling it is optional.
If the parameter C_SKIP_PROCESSING_WITH_SUCCESS is set to true, the normal inbound processing for the received document is skipped and a success message is reported to the partner system and logged locally. By this means separate inbound processing can be implemented in the BAdI.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20070130 |
| SAP Release Created in | 700 |
