Home | ERP Applications without HCM | Trading Order Processing | Trading Order
|
|
Home | ERP Applications without HCM | Trading Order Processing | Trading Order |
Search |
||
Related Information |
||
| Where used | ||
ES Workplace Basket |
||
|
Open Basket
Add to Basket |
||
| Software Component Version | ESM ERP 606 |
| Technical Name | TradingOrder |
| Business Object Type | Business Process Object |
| Release Status | Released |
Usually in a trading company, one person or department carries out both buying and selling activities. A common data entry screen for both purchasing and sales data is essential to avoid redundant data entries and reduce missed operations.
The Trading Order business object enables entry of data for either sales or purchase orders or both, either simultaneously or separately using a single transaction. The trading order can support both one-sided and two-sided (back-to-back) purchasing and sales transactions. The Trading Order business object forms the basis for all purchasing, sales, and expense processes and provides a clear overview of and process control for all related business transactions. As it takes into account purchasing prices, sales prices, and expenses, the trading order allows you to perform profitability simulation immediately. When a trading order is released, the system creates follow-on sales and purchasing documents.
For the sales and purchasing side on item level, commodity future items can be managed with securities, quantites, and delivery periods. For a fixing date and a fixing quantity, these future items for provisional price components and for other price components are created, whereas for the normal price components, a price specification can be given.
Trading contract (synonym in SAP Module 'EA-GTM')
Other Terms
Trading contract (synonym in EA-GTM)
B2B- and A2A-related information:
As an example, an SAP ERP back-end system could be called by a third-party front-office commodity system, and the trading order could be created using a SOA service.
