> Transactions

AGR_USERS – список ролей юзера
UST04 – список профилей авторизации юзера
USGRP_USER – список групп юзера

TSTC – список всех транзакций (фильтр, маска)
CDHDR / CDPOS – просмотреть удаленную поставку (* OBJECTID *)
T030 – сопоставленный счету класс оценки
C001 – сопоставленный счету Acct assignment grp
MBEW – valuation, average prices
MBEWH – история изменений MBEW
TNAPR – NACE какой output тип к какой condition привязан
D010TAB – по имени таблицы найти в каких транзакциях/программах эта таблица используется
SMEN_BUFFC – „Избранное“, Favorites SAP Menu
SE16N_CD_KEY – SE16N changelog (SE16N_CD_DATA – данные)

Output type tables (B0XX…):

B000 $ Sample Table for output control
B001 Sales Organization/Customer Number
B002 Output Control: Sample Structure for Output Data
B005 Sales Organization/Order Type
B006 SOrg/DstCh/Division/Customer
B007 Order Type
B008 Output Control: Sample Structure for Output Data
B009 Output Control: Sample Structure for Output Data
B010 Shipping Point/Route
B011 Output Control: Sample Structure for Output Data
B012 Output Control: Sample Structure for Output Data
B013 Output Control: Sample Structure for Output Data
B014 Output Control: Sample Structure for Output Data
B015 Credit Control Area/Cred.Representative Group/Risk Category
B016 Labeling
B017 Transport type
B018 Sales Organization/Receiving Country
B020 Shipping material type
B021 DlvType/Shipping Point
B022 TrspPlPoint and Shipment Type
B023 TrspPlPoint, TrspProcessingType and Service Agent
B025 Purchasing Output Determination: Doc.Type/PurchOrg/Vendor
B026 Purchasing Output Determination: Document Type
B027 Purchasing Output Determination: Purch. Org./Vendor for EDI
B028 Ship-to party/shipping mat.
B030 Specification Department
B031 Area of Responsibility
B032 Application Area: Output Number
B033 MRP Controller
B034 Planner Group
B035 Plant
B040 Document Type/Document Status
B046 CoCode, Blocking reason: Price
B048 CoCode, Vendor
B049 Company code
B050 Output Control: Sample Structure for Output Data
B055 C Status, Laboratory
B060 PM Message – Plant Maintenance
B061 Purchasing Group
B062 Laboratory/Engineering and Design Office
B063 Planner Group
B064 Capacity Planner
B065 MRP Controller
B066 Cost center
B070 Event/print vers./print ind./label type/label form
B071 GR Output
B072 Event/Print Vers./Print Ind.
B073 Event/Print Vers./Print Ind./SHKZG
B074 Missing Parts
B075 Kanban Cards for GR
B100 Output Determination: DocumentType/Purch.Org./Material Group
B120 Condition tables for Output Nota Fiscal
B121 OutputDev.
B150 Doc.Type/Sales Org./Customer
B160 Sales Organization/Condition Granter
B161 SOrg/Distr.Channel/Division/Rebate Recipient
B170 Purchasing Organization/Invoicing
B171 Sales Organization/Distribution Channel/Division/Payer
B172 Company Code/Invoicing
B173 Company Code/Payer


Access a transaction without authorization (skip check)

All the problem related to running a SAP transaction can now be resolved with the help of execution of a debugger.
One of the major advantage of using the debugger is that while any changes are being made all those can be recorded in a log.
Various ways to skip the authorization check:

  1. Within Function module ‚SMTR_KERNEL_CHECK_AUTHORITY‘ insert a break-point. Press F7, clear the variable P_CANCEL_FLAG.
  2. Within Function module ‚RS_TRANSACTION_TEST‘ insert a break-point on the ABAP code line ‚if sy-subrc = 0.‘, straight after the call ‚AUTH_CHECK_TCODE‘ id ‚TCODE‘ field objectname. And change sy-subrc to 0.
  3. Just run any transaction using functional module SMTR_KERNEL_CHECK_AUTHORITY (still works if correcting Note was not implemented).

P.S. Can’t run FM’s but can run programs? Just run the RSFUNCTIONBUILDER program.

Determination rules

N/ Determination object Rules for determination
1 Sales document Sales Area
+ Document Type
2 Item category determination for Sales document Document type
+ Item category Group
+ Usage
+ Higher level Item Category
3 Schedule line category determination Item category of the corresponding item
+ MRP type of the Material
4 Delivery document determination Delivery document default type attached to Sales document type
5 Item category determination for Delivery document Copy from Sales document
Delivery Document type
+ Item category Group
+ Usage
+ High level Item Category
6 Shipping Point Determination Delivery Plant
+ Shipping condition (Customer Master – Sold-to Party)
+ Loading group (Material Master)
7 Route determination Departure zone of the shipping point (Customizing)
+ Shipping condition (SP)
+ Transport group (MM)
+ Transportation zone of the Ship to party (General Data)
8 Storage location determination Shipping point
+ Delivery plant
+ storage condition
9 Picking determination On bases of MALA rule
Delivery Plant
+ Loading Group
+ Storage condition (MM)
(storage rule also assignment to Delivery type)
10 Packing determination Package usage
11 POD This object use for confirmation of delivery, based on which billing document can create
12 Billing document determination Sales document type is maintained as default type
For Billing plan, Billing Type maintain under Billing Plan Type of Maintain Date Category for Billing Plan Type
13 Account determination Chart of Accounts
+ Sales Organization
+ Customer Account group (Customer Master – Payer)
+ Material Account group (Material Master)
+ Account key
14 Business area determination Plant/Valuation Area
Sales area
Item division + Plant
15 Company code determination Sales organization uniquely attached to Company code
16 Partner determination At -Account group level, sales document header level, item level, sales document delivery level, Shipment level, Billing document level and item level
17 Delivery Plant determination The system will determine Plant details at following in given sequence
Customer – Material info record
From Customer master Ship-to Party
From Material Master
18 Output determination Output determination at Sales document level, Delivery level, Billing level
19 Price determination Pricing procedure
Sales Area
+ Document Pricing Procedure indicator from Sale/Billing Document type
+ Pricing Procedure indicator from Customer Master (Sold-to Party)
20 Text determination 1) Customer Material Information Record
2) Customer Master (General text, Accounting text, Sales text)
3) Material master text (Sales text or PO text)
21 Warehouse determination Warehouse number
+ Plant
+ Storage location
22 Lean Warehouse determination Lean warehouse activate,
+ Storage Location
+ Warehouse number
23 Tax determination Destination Country of Ship-to Party
+ Departure Country of Shipping Point
+ Tax Classification for Customer from Customer Master
+ Tax Classification for Material Master
24 Routing determination Shipping point
+ Delivery plant
+ Loading condition
+ Shipping condition
25 Material determination Create condition record
Maintain Customer Material record
26 Product substitute Create condition record
27 Product Exclusion Create condition record (Not to sale any particular product)
28 Product listing Create condition record (Sale of one particular product)
29 Credit check Credit check at Sales document level OR at Delivery OR at Good issue Risk group at Sales document level and Risk category from Customer Master, Item category credit check should be activate
30 Incomplete log Incomplete log assign to Status group, which is assign to Sales document, Item category or Schedule line level
31 Rebate condition setup Customer master billing info checked, Sales organization activate, Billing document activate





Error sending message for document.

SAP notes 1575263, 1585239

Data Replication Framework (DRF) – tx. DRFIMG

SAP SD books


„Implementing SAP ERP Sales & Distribution“, Glynn C. Williams, 2008

„Configuring SAP ERP Sales and Distribution 2010“, Kapil Sharma, Ashutosh Mutsaddi, 2010


„100 Things You Should Know About Sales and Distribution in SAP“, Matt Chudy, Luis Castedo, 2012

Common SAP R/3 functions manual, 20.1 Mb

  • ABAP Development for Sales and Distribution in SAP (Exits, BAdIs, and Enhancements), Michael Koch
  • What on Earth is an SAP IDoc – Jelena Perfiljeva.pdf

There are four books related to SAP SD Certification – TSCM60 (parts 1 & 2) and TSCM62 (parts 1 & 2):

SAP: Кто хочет на новый проект с командировками?

(суммарно эта страница весит 50 мб)

Read the rest of this article

History of material planning

How do we have planned materials until of PC-epoch?

Materials management
Is a concept to which I’m devoted —
Instead of learning production control,
I’ve escaped and getting promoted!

So study each book and seminar,
Attend every one you can, sir!
You’ll find a thousand experts —
each with PART of the answer.

Oli Wight, „Production Control Experts“

Materials management started out as part of the production manager’s function.
It was imperative for managers to understand the location of the needed components to finish their required schedules. Without some tracking and knowledge of the supply-chain activities, there was little chance of timely success.
Henry Ford was probably one of the first managers to get a tight handle on his supply chain. He was in the lean material space and didn’t even know it.
His approach was vertical integration, which was an advantage in those early days. „The thing is to keep everything in motion and take work to the man and not man to the work. That is the real principle of our production, and conveyors are only
one of many means to an end. (Today and Tomorrow, Henry Ford, 1926, reprint Productivity Press 1988).
Ford continues, „The motor block is the heaviest casting used in the car.
It was formally manufactured at Highland Park, but it was a waste to transport these castings to Highland Park and then ship the completed motors out by rail to the branches past the very gates of Fordson.” So what did he do? He transferred the motor assembly to Fordson, putting it in a building 800 by 600 feet where there were four main assembly lines or conveyors. The process of making the motors became continuous. He knew the concepts of lean materials management in the early 1900s. Toyota Production System (TPS) experts have acknowledged the thinking of Henry Ford more than once. This early concept of the conveyor belt bringing material to the worker is precisely the concept behind lean materials management. Add to it the additional process of building only what is required for customer consumption, and waste becomes a lesser evil.
Jumping ahead to the 1980s, the Japanese influence gives rise to new thinking in the material management space with the concept of just-in-time (JIT) material.
Kanban systems were introduced as methods to allow rapid communication between suppliers and users/customers for material movement and to supply
demand fitted exactly to the need. This eliminated much of the waste created by stocking inventory on forecasted requirements. This new thinking, made famous by Toyota, migrated the Western thinking that only a few containers meant too little inventory to the Toyota view that if many containers existed, it meant too much inventory! This was truly revolutionary in the 1980s. Few North American manufacturing organizations at that point fully recognized this opportunity.
In the West there was another revolution starting—the rise of the computer. Material Requirements Planning (MRP), invented in the 1970s, was evolving and developing in the 1980s and would greatly influence the planning of material flow and materials management. Although a far cry from today’s definition of lean materials management, MRP, nonetheless, did help eliminate a tremendous amount of inventory in most production facilities. It might now be said that in those early days, MRP helped businesses go from absolutely no material control to bad control! It was a huge jump forward, however.
According to the Production and Inventory Control Handbook (James H. Greene, 1987; p. 4.2), MRP was used first by J. I. Case, Twin Disc, Black & Decker, and Perkins-Elmer. According to this text, the American Production and Inventory Control Society (APICS) and a few pioneer organizations started the MRP revolution in the early 1970s. MRP was a simple idea. Bills of material (BOMs) that defined the recipes of the products created the requirements. Inventory records were then accessed and requirement quantities netted against available balances. Using the MRP software, the delta between requirements and on-hand balances generated signals for purchase orders and shop orders.

This innovation slowly led to a greater use of centralized computers and more controls built into manufacturing and planning systems. Manufacturing Resource Planning (MRP II) methods were next in the evolution. MRP II happened as many evolutions do—from need. Humans often do not change radically unless forced to in some manner. In the 1980s, manufacturing was forced in a big way. Interest rates were sky rocketing and businesses were getting pressure from many fronts. Competition from other parts of the world was becoming more real and prices reflected it. This included some of the Japanese companies that were learning to build unheard-of quality into their processes. The need to cut costs and, therefore, become more competitive drove materials management professionals to look for better and more efficient methods to plan material deliveries. It wasn’t just for the sake of continuous improvement; it was a matter of survival. This effort led to more discipline on data inputs and files accuracy. According to the Production and Inventory Control Handbook (Greene, 1987; p. 4.8), the acronym MRP II was first documented in Modern Material Handling in 1979.
The article described activities going on in Tennant, Twin Disc, and Hewlett-Packard as integrating their financial and operational processes.
Standards of excellence within the planning processes were also developed in this period. The term Class A MRP II had become a desired recognition, and consultants like the Oliver Wight group were building businesses on Class A MRP II process with its corresponding certification. The early certifications only required that a handful of operational metrics be at 90% performance or higher.
Crude, and not close to today’s required competitive standards, it was one of the first definitions of high performance in the materials management space.
Materials management had changed course forever by this point. There was no going back to the days of unrecognized waste. The new emphasis had begun— make only what is needed and clearly define those needs. Those businesses were still a long way from lean, but they were getting closer. In the 1980s, because of cost constraints and competitive pressure, businesses placed more emphasis in the areas of capacity planning and increased scheduling disciplines. It was getting more and more important to build and to stock the right inventory.
With the success of Toyota penetrating Western markets in the 1980s, the world took notice of the techniques that had been evolving in Asia.
The late Dr. Shigeo Shingo was one of the more important figures to revolutionize the management of production and materials. With the introduction of Single Minute Exchange of Die (SMED), many methods of lot sizing, specifically Economic Order Quantity (EOQ), became obsolete. Although some companies recognized this in the 1980s, realistically it was well into the 1990s before Western manufacturing fully understood this fact. Again, it was only through being forced into change. Competition forced major changes in thinking.
The word „can’t“ was being tested continuously.
In the twenty-first century it is fully recognized that not only is lean materials control necessary but so is change. Without continuous improvement, companies cannot stay ahead of their competitors or, in some cases, even stay with them! Without keeping material moving into the process, and at the same time limiting the unnecessary movement, maximum efficiency is unrealistic. It sounds like manufacturing has come full circle with Henry Ford—same ideas, just at a higher level of performance expectation.


Through normal process evolution and help from software providers and their marketing efforts, MRP II became Enterprise Resource Planning (ERP) in the 1990s. It was acknowledged that times were changing and, therefore, acronyms needed to change also. Normal ratcheting of requirements and expectations led to the upgrading of MRP II methodology.
This transformation in name did not take long once started. High-performance standards followed quickly on the heels of Class A MRP II.
Naturally, the scope of the Class A performance standard grew with the competitive pressures, and because the market was asking for ERP rather than MRP II, Class A MRP II upgraded its moniker to Class A ERP in the late 1990s.
The ERP model encompassed the entire business model, including linkage to the supply chain through to the customer (figure 1.1). Materials management, especially lean material management, was a critical part of the ERP business
model. Although developing throughout the 1990s, it was late in that decade when lean materials management started defining the new role of MRP and the Toyota principles of lean manufacturing.

Figure 1.1. ERP Business System Model

ERP today is often confused with software. APICS defines ERP as both process and software. Some argue with the software part of the definition, stating that software is only the planning enabler and that good ERP process starts and ends with robust process design, dependable management systems and disciplines, and repeatable execution. Lean materials management cannot be divorced from any of those keys.
It is part and parcel of good ERP performance. Starting with top management planning and following through to customer satisfaction, materials management is in the middle of the fray.
When organizations do a good job with ERP execution, the materials management is at the center of the planning and success.
Robust ERP execution encourages top management to have well-mapped strategies, including markets, products, and inventory strategy
(e.g., make to stock, make to order), and have capacity and capital plans in place as well.
Materials professionals within the business facilitate the inventory decisions by providing models and proposals.
Following closely, the handshake between the demand side and the supply side of the business must risk-manage the commitment of supply-chain resource.
Again, the materials management is involved because proposals to position inventory are usually suggested for scrutinization during these planning sessions.
In some organizations the master scheduler organizationally reports to the materials group and, in those organizations, materials management owns the show from proposal to execution. Only approval and associated adjustments are outside their roles.
In ERP environments this comes as no surprise. After all, the „P“ in ERP does stand for planning and materials management is the planning center for manufacturing organizations.
The top management planning process during which the demand and supply sides of the business meet once a month for risk assessment and analysis is called the Sales and Operations Planning (S&OP) or Sales, Inventory and Operations Planning (SIOP) or even Production, Sales and Inventory (PSI) process by most companies. The master scheduler, or sometimes the materials manager, normally prepares the S&OP formats and data for the meeting. Metrics are reviewed to determine the accuracy of previous plans so that adjustments can be made to improve the predictability of the process and to minimize risks. The results of this planning process are 12-month rolling requirements that drive supply-chain signals for the next 30 days until the team gets together for a follow-up review. It is an age-old proven process in all high-performance organizations and the materials management is in the middle of it. Chapter 7 details the S&OP process and the mechanics behind it.
Once the S&OP process has authorized the supply-chain risk, the master schedule in an ERP process is released, sending the new 12-month rolling updates to the connected world through the materials plans and supply-chain links.
Today this is often executed through secure and confidential web pages designed to give access and information to key suppliers and partners several times a day.
Information includes forecasts of shipments, configurations of model breakdown and, often, existing stock for materials provided by that particular supplier.
In less sophisticated web links, only the unit build forecast is shown (figure 1.2).
This web information is the result of materials management activities.
Depending on the level of detail, it is either an output of the master schedule or an output of MRP.
The format can be in weeks (figure 1.2), days, or even hours in some supply chains, depending on the quantities and tightness of inventory control. The detailed schedule information in SKU format would be a separate feed.
In some arrangements there is only one communication, the detailed version.

Figure 1.2. Weekly web-based communication example.

There is no generic right or wrong way to communicate direction to the supply chain in an ERP environment,
but it must be in the correct level of detail for the market and environment.
In the automotive supply chain, the details could be communicated in hours; in other supply chains, days could be enough;
still others forecast in weeks and months; however, the detailed schedule is generated in days and communicated separately.
In one appliance manufacturing environment, the drumbeat is communicated each day on a web tool with requirements stated in hours.
In this same environment, the 12-month rolling (long term) plans change once a month but the detailed (short term) plans are updated hourly.
Several of the ERP linkages that must happen in high-performance companies have now been described (figure 1.3).

Figure 1.3. Linkages in ERP process.

Once the link is made to the supplier, the process flow has only begun.
There are still numerous communications and controls required in a high-performance ERP process.
The next link is to the shop floor, both internal and to the supplier’s shop.
Lean is a more recognizable element in this section of the ERP model. Here, we might not use web-based tools.
Simpler tools, including visible factory boards, kanban cards, lines painted on the floors, or limited rack size can be utilized.
Now, lean materials management gets exciting and fun! More detailed information is found in the next chapter,
but right now the objective is to continue to map the ERP process. Think for a minute about where we are in the process discussion.
If looking at this from the perspective of the customer, we would be communicating the signal to the supply chain.
What about when we are the supplier in the
transaction? The perspective now becomes a customer signal through the demand side of the process map and the ERP business model starts from the top again.
It doesn’t stop until the supply chain comes to the consumer product.
Everything starts with dirt and ends up a consumer product!
Some would argue that the consumer product often ends up back to dirt.
At least the biodegradable ones do! Think of it. All supply chains start with raw materials which usually involve chemicals (dirt related) or elements (found in dirt) or plants (plants get nutrition from dirt) or animals (animals connect down the food chain eventually to plant eaters or plants and, of course, dirt). ERP encompasses all of that activity through the entire food chain from dirt to dirt!
Understanding lean methodology allows that massive energy expenditure to be as efficient as possible.

ERP is the model that all businesses follow throughout the supply chain.
Some do it better than others, of course. Some do it and wouldn’t admit it because they are not all that versed in the formalities. Lean is often substituted for a business model. Lean and ERP are not of the same genus and species. One (ERP) is a process model; the other (lean) is a tool and/or focus. Lean ERP is the high-performance organizations’ focus. In these organizations, lean materials
management is making improvements to the process and increasing performance through the supply chain.
It is from this perspective that the discussion on lean materials management is built.
Good manufacturing process requires the elements of ERP—top management planning, demand and operations planning,
master scheduling, material planning and execution. Done in the most competitive format, a lean process focus is evident in each step of the ERP process model.

Sounds easy but it is not as easy as it sounds.

© Lean Materials Planning and Execution: A Guide to Internal and External Supply Management Excellence
Donald H. Sheldon
J. Ross Publishing, 15 Nov, 2007



Product ID is represeneted in a couple of different formats in SCM – and hence in EWM.

Table /SAPAPO/MATKEY contains a MATID (Internal Number (UID) for Product), which consists of 22 characters which is a mixture of upper and lower case letters as well as digits.

On the other hand in EWM most tables and references refer to materials via hexidecimal numbers with length 16 (32 characters).

Function module /SCMB/MDL_GUID_CONVERT can be used to convert between these two formats.

© John Kristensen


> Transactions
> Tables

  1. Q: Are There any User Exits to include new fields in the Sales Order?
    A:Follow path : IMG->SD->System Modifications->User Exits. There you can click on the help document and it will show all the user exits with program name. Select the suitable one.
  2. Q: What criteria does the delivery split based on?
    A: As per standard SAP functionality delivery will split based on the following criteria:
    – Shipping Point
    – Ship to party
    – Delivery Date
    – Incoterms
    – Unloading Point
    – Route
    P.S. SAP Delivers report „ZLE_ANALYZE_DELIVERY_SPLIT“ to analyze the reason for delivery split.
  3. Q: How to open table for editing, &SAP_EDIT not working?
  4. Q: Where is the indicator that delivery was distributed or confirmed and so on?
    A: Field LIKP-VLSTK:
    Not Relevant
    A Relevant
    B Distributed
    C Confirmed
    D Planned for Distribution
    E Delivery split was performed locally
    F Change Management Switched Off
  5. Q: Whenever I run SAP Netweaver Developer Studio 7.3 I get error JVM terminated Exit
    A: The installer of SAP Netweaver Developer Studio was 32 bit and it required JVM to be 32 bit.
  6. Q: Create physical inventory document for material, it has an error message „Storage location for material’s valuation type does not exit“
    A: If you want to make a physical inventory for a material valuated separately, you have to proceed as follows: – make a goods receipt (MvT 561) and the stock segment will be created – make the reversal of the goods receipt – make the inventory.
  7. Q: How to extend Field Catalog for Condition Tables?
    A: Maintain fields in the Customizing view V_T681F with the following: Usage ‚A‘, Application ‚MS‘, Field Group ‚001‘. Then the fields will be available to create the conditions. In case of ZZ-fields, you have to add them first into structures KOMKBME and KOMB-structure’s incl.KOMBZ
  8. Q: How to set default printer LOCLRUS for ME9F?
    A: [MN05] – NEU – Purch/Doc vs Purchasing Org – NB / [Plant] – Funct-VN, Medium-1, Date/Time-3, Partner-empty. Save.
  9. Q: What is correction delivery (LFKO)?
    A: You correct cumulative quantities in scheduling agreements:

    • In case of returns
    • When there has been a processing error
    • When there has been a year change
    • When you are transferring initial quantities from a legacy system into the SAP System

    To do this, you create a correction delivery within the delivery schedule itself. This delivery is not relevant for requirements planning, shipping, goods issue, or billing. Correct cumulative quantities only when the customer has not posted goods receipt.

  10. Q: How to find roles by release code (BANF)?
    A: Use table AGR_1251 and object M_EINK_FRG:
  11. Q: Error: There is already a handling unit &1 posted for GR without stock
    A: Just delete the HU using HU02.
  12. Q: How to debug print forms?
    A: Use brackpoints in modules FP_FUNCTION_MODULE_NAME, FP_JOB_OPEN and FP_JOB_CLOSE
  13. Q: How to (re)generate Function Module for PDF-form?
  14. Q: ABAP regex to remove trailing zeroes with decimal point?

/i – удалить текущую сессию
/o – список сессий
/nend – выйти из системы
/nex – выйти из системы без подтверждения
Зажав Ctrl и щёлкнув правой кнопкой мышки над полем у которого нет истории – в появившемся контекстном меню появляется пункт „Активировать историю“.

Виды движений:
101 – приход
102 – сторно приход
201 – списание в брак (на МВЗ)
261 – backflush (декларирование производство)
262 – Сторнирование списания в производство
309 – Перевод из материала в материал
311 – трансфер со склада на склад

321 – QI to unrestricted
322 – unrestricted to QI

344 – unrestricted to blocked
343 – blocked to unrestricted

349 – blocked to QI
350 – QI to blocked

453 – returns to unrestricted
457 – returns to QI

701 и 702 – Инвентаризация
601 – отгрузка

Список движений

  • Кроме обычного соединения с SAP системой, можно сделать соединение с конкретным мандантом, конкретного пользователя и конкретной начальной транзакцией. Делается это через кнопку  на панели инструментов SAP GUI. Появится экран, куда вы можете все прописать. При запуске такого ярлыка у вас будет запрашиваться только пароль для указанного пользователя (способ, как сохранить и пароль пользователю описан в SAP note #146173).
  • Меню пользователя с отображением технических имён транзакций – в меню Дополнительная информация – Параметры настройки отмечаем флаг „Отображать техническое имя“.

SAP GUI 7.30 для Linux перевыложен – скачать можно по этой ссылке:

Q: Как определить какой порт использует server SAP, чтобы соединиться к нему?
A: В стандартном порту 3200 последние две цифры замените номером системы (10 в примере ниже).

Q: Как в SAP GUI for Java создать соединение с необходимыми мандантом/группой/системой?
A: В expert-mode строке соединения
параметры означают следующее:
/H/prd.eu.merben.com – хост
clnt=101, 3210 – клиент, порт
/G/LogonGroup14 – группа
/R/ITP – система

Button Shortcut Description
Клавиша „Ввод“ (Enter) Далее (Enter/Continue)
Ctrl+S Сохранить (Save)
F3 Назад (Back)
Shift+F3 Выход из задачи, системы (Exit)
F12 Отмена (Cancel)
Ctrl+P Печать (Print)
Ctrl+F Поиск, найти (Search, Find)
Ctrl+G Искать далее (Continue search)
PageUp На страницу вверх
Page Down На страницу вниз
Ctrl+Page Up На самый верх документа (To top)
Ctrl+Page Down К последней странице документа (To last page of document)
Ctrl и „+“ Запустить новую сессию (Create New Session доступно и из системного меню Alt+пробел)
Ctrl+F6 Отобразить результаты (Display results)
Alt+F12 Настройка внешнего вида (Customize local layout)
F8 Запустить / исполнить (Execute)


SD Training Curriculum

Day 1


Introduction, SAP, GUI, Versions, Modules

Day 2

ASAP Methodology

Day 3

System Landscape

Day 4

Transports, Customization, Configuration

Day 5

General explanation of Inquiry to Cash Cycle, Enterprise Structure, Customer Master etc.

Day 6

Master data

Customer Master, Material Master, Customer Material Info Record

Day 7


Day 8

Credit management, Accounts

Day 9


Day 10

Text, Incompletion log

Day 11


Sales documents

Day 12

Delivery documents

Day 13

Billing documents

Day 14

Copy Control

Day 15

Item Categories, Schedule lines

Day 16


Standard ITC / QTC/ OTC Cycle

Day 17

Return Scenario, STO

Day 18

Availability Check, Transfer of Requirements

Day 19

Sales BOM, Intercompany, 3rd Party

Day 20


Day 21



Day 22


Day 23

OSS Notes

Day 24

SD Tables

Day 25

Routines, User Exits

Day 26

Getting Ready


Day 27

Online help – SAP help site, forums, SDN, BPX

Day 28

Resume templates

Day 29

Mock Interview / tips for technical screenings, face to face interviews

Day 30

Certificate of Completion