Article 46: What are PR Document Types and how do they control processing?
What is a PR Document Type?
A PR Document Type is a crucial control key that differentiates between various types of requisitions and determines how they are processed, numbered, and approved within the system.
What does Document Type control?
Number Range Assignment:
- Internal numbering - system assigns PR numbers automatically
- External numbering - users enter their own PR numbers
- Number sequence - ensures unique identification
Item Categories:
- Which types of items can be requested (materials, services, etc.)
- Account assignment options available
- Special procurement types allowed
Approval Workflow:
- Release procedure - who must approve the PR
- Approval levels based on value or material type
- Routing rules for different scenarios
What are common Document Types?
Standard Document Types
NB (Standard Purchase Requisition):
- Most common type for regular material requests
- Internal numbering with automatic assignment
- Standard approval workflow
- All item categories allowed
ZNB (Custom Asset Purchase):
- Specialized for asset acquisitions
- Enhanced approval process for high-value items
- Specific account assignment requirements
- Additional documentation fields
Specialized Document Types
Stock Transport PRs:
- For materials moving between plants
- Special processing rules for inter-company transfers
- Different approval requirements
- Integration with logistics planning
Service PRs:
- Service-specific item categories
- Service master integration
- Performance-based approval criteria
- Contract reference capabilities
How to choose the right Document Type?
Consider these factors:
- Type of procurement - materials, services, assets
- Approval requirements - standard vs. special approval
- Value thresholds - different limits for different types
- Account assignment - cost centers, projects, orders
- Company policy - specific rules for certain categories
What happens if I choose wrong Document Type?
Potential issues:
- Approval routing to wrong personnel
- Missing fields required for processing
- Incorrect numbering causing confusion
- System errors during PO conversion
Best practices:
- Understand your options before creating PRs
- Follow company guidelines for document type selection
- Consult with purchasing for complex requirements
- Use consistent types for similar procurement scenarios