Download
1 / 34
370 likes | 629 Views
Manufacturing game. Part 1 - Chapter 2 Introductory game. Objective. The objective of the introductory game is to provide a quick hands-on experience of an integrated business process in order to get an overview of both the ERP simulation game and of the SAP system. Your 6 products.
E N D
Manufacturing game Part 1 - Chapter 2 Introductory game
Objective • The objective of the introductory game is to provide a quick hands-on experience of an integrated business process in order to get an overview of both the ERP simulation game and of the SAP system.
Your 6 products 40% wheat 40% oat 20% nut 1 box 1 bag 40% wheat 40% oat 20% raisin 1 box 1 bag 40% wheat 40% oat 20% blueberry 1 box 1 bag 50% wheat 50% oat 1 box 1 bag 35% wheat 35% oat 10% raisin 10% nut 5% strawberry 5% blueberry 1 box 1 bag 40% wheat 40% oat 20% strawberry 1 box 1 bag
German market North DC10: 2 retailers DC12: 19 retailers West DC10: 3 retailers DC12: 17 retailers South DC10: 7 retailers DC12: 23 retailers
Welcome to your new job ! http://www.youtube.com/watch?v=XYFJASoYGps
30 min 30 min 30 min 30 days 30 days 30 days Game layout – Four Quarters
Rules of the game • Each quarter will be of 30 virtual days (approx 1 min per day) • End-of-quarter inventory is carried over to the next quarter • You can sell a product only if you have it in stock • You compete against the other teams and importers • Your objective is to MAXIMIZE PROFIT
ABC of Enterprise systems • An enterprise system is build around an integrated database • A system such as SAP contains tens of thousands data tables • When a user creates, changes or views data in the system, he or she performs a transaction • Data changed or created by one user can be exploited by all other users (ex. reporting, tracking, execution of orders, etc.) • All transactions are traceable, transactions with financial impacts can be reversed, never erased
User interface • Users interact with the enterprise system through transactions. • A large number of pre-programmed transactions exist in SAP • Each transaction has a transaction code – one can call a transaction if one knows the transaction code • The SAP menu allows to browse and find the desired transaction • One can create a user menu or a list of favourites with the commonly used transactions
Participant’s job aid – Extended Game First Simulation Must Use Transactions Optional Transactions Reports
SAP Menu & Navigation Extras / Settings / Display technical names
Reports and queries • Reports and queries are transactions that allow users to view existing data • A typical query is performed as follows: • In the first page of the transaction, you must enter the selection criteria for the query (ex. Company code, product code, etc.) • Then, click on to execute the query • A table containing the requested data will appear • The display and layout can sometimes be modified
Entering new data • Some transactions are designed to change or create new data (change forecast, release purchasing orders, change sale price, etc.) • The interface varies according to data required by the system • The system will not allow you to save information if all the compulsory fields have not been filled • You must save/release/confirm before exiting the transaction
Other useful buttons • Use the navigation buttons to go back or get out of a transaction • You can open up to 6 sessions. Click on to open a new session • Delete , search , select all , view , enter .
The Introductory game:Quarter 1 (30 virtual days) • You need to maintain the price of your 6 products and invest in marketing. • What do you need to know in order to make that decision ? • You need to know how to : • Maintain price list • See available stock • Monitor sales orders • Monitor competitors • Monitor your profit !
