-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- IDOC communication between different basic type re...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
IDOC communication between different basic type releases.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Mar 27 5:08 PM
- SAP Managed Tags
- ABAP Connectivity
Has anyone run into a scenario where a newer SAP release would like to send a message to a partner with an older SAP release, using a basic type that does not exist in the older system? (eg. DELVRY05 which only exists in release 700)
In this scenario, what is the best practice, other than to have the newer SAP system send an older basic type that does exist in the receiving partner?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Mar 28 4:37 AM
- SAP Managed Tags
- ABAP Connectivity
Hi,
You can do this by specifying the older release in the partner profile outbound settings (for message type).
Under the "Outbound options" tab there is a field "Seg. release in IDoc type". There you can specify the older release and the IDoc will automatically be depricated when it is received in the receiving system.
Regards,
Gajendra.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2007 Mar 28 4:37 AM
- SAP Managed Tags
- ABAP Connectivity
Hi,
You can do this by specifying the older release in the partner profile outbound settings (for message type).
Under the "Outbound options" tab there is a field "Seg. release in IDoc type". There you can specify the older release and the IDoc will automatically be depricated when it is received in the receiving system.
Regards,
Gajendra.
Bluesky