Hierarchy

⤷

⤷

IMG Activity
ID | /IPRO/MATERIAL | Trigger Approval Workflow |
Transaction Code | /IPRO/67000062 | (empty) |
Created on | 20070105 | |
Customizing Attributes | /IPRO/MATERIAL | Trigger Approval Workflow |
Customizing Activity | /IPRO/MATERIAL | Trigger Approval Workflow |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /IPRO/MATERIAL |
Use
This Business Add-In is used in the Document Builder component (CA-GTF-DOB) to distinguish major changes from minor changes in a released document or element. As far as elements are concerned, the version number of all elements must be '0' (active) when you perform an upgrade. If not, your System Administrator must convert all elements. For changes requiring workflow approval a new element version is created, whereas changes not requiring workflow approval apply to the current element version.
This Business Add-In consists of the two methods described below:
MATERIAL_DOC (Document level changes)
The following import parameters are required:
- pio_pre_doc type /ipro/if_document
- pio_new_doc type /ipro/if_document
The following are the export parameters:
- pev_message type bapiret2
- pev_wf type seu_bool
MATERIAL_CLAUSE (Element level changes)
The following import parameters are required:
- pio_pre_element type /ipro/if_docb_element
- pio_new_element type /ipro/if_docb_element
The following are the export parameters:
- pev_message type bapiret2
- pev_wf type seu_bool
This Business Add-In has no fallback class or implementation, and is for single implementation use only.
Requirements
You are free to implement this Business Add-In. You can make minor changes to a released document when they do not require workflow approval. Major changes, however, require approval. The implementation allows you to describe major changes such as text or date changes, then compare the two documents or elements. In either method, if a major change is found, the PEV_WF export parameter returns an 'X'. An internal local class will try to execute an existing implementation. If no implementation exists, the execution is skipped.
Standard Settings
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Business Attributes
ASAP Roadmap ID | 251 | Transport Customizing for Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | /IPRO/MATERIAL | 0 | HLB0009110 | Cross-Application Components |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20070504 |
SAP Release Created in | 300 |