SAP SD complex instructions – Seite 4

26 06 2015

SAP SD Certification Exam (130 questions)

Spoiler: Large HTML table.

c. The availability control screen will be displayed	During the sales order processing, a user will be alerted when stock is not available for material entered in the sales order if the availability check was carried out. In which of the following ways will the user be alerted about the situation?
	a. An error message will appear on status bar alerting the user to the situation
	b. The selected line will be marked and highlighted by the system
	c. The availability control screen will be displayed
	d. The incompletion log will display the unconfirmed schedule line as a missing field
b. Sales order number c. Terms of payment d. Payer	In the standard system, which of the following can be used as splitting criteria when creating an invoice?
	a. Account group
	b. Sales order number
	c. Terms of payment
	d. Payer
	e. Sold-to-party
a. Whether document number is external or internally used c. Whether an item is blocked for delivery d. Whether a delivery document is created automatically	Which of the following does the sales document type control? (3)
	a. Whether document number is external or internally used
	b. Whether an item is to be delivered
	c. Whether an item is blocked for delivery
	d. Whether a delivery document is created automatically
	e. Whether availability is checked

21 05 2015

SAP customer list in Russia

Ruslan Customer clients, der Kunde, Клиенты SAP в России 0

SAP customers in Russia:

Surgutneftegas
X5 Reatil Group
IDGC of Centre (МРСК)
MRSK Urals
Lebedyansky
Невская косметика (NC)
Komus
Uralsib
Mostransavto
Pension Fund of the Russian Federation
4lapy
Sunway Group
OAO Slavneft-MegionNeftegaz
Promsvyazbank
MOEK
TNK-BP
MODIS
Produkty Pitania
SUN InBev
OAO OMPK
Severstal
Tactical Missiles Corporation
Smart Value
MEKRAN
Noringa
Восток-Запад
Gorenje
Vostok-Servis
BEKO
Aeroflot
Lenta
585
Russian Railways
MVIDEO
Togas
Bezant (ТК БЕЗАНТ)
Victoria Group
Vympel NPO
Synergy
Megapolis (gkm.ru)
MKB Raduga
Велком (Velkom)
Fix-Price
Eldorado
SaratovStroySteklo
ROLF (group of companies)
Megafon
Detski mir
Svyaznoy
Rostselmash
Yuterra
Sberbank
Euroset
Rosneft
Cherkizovo group
Ulmart (Юлмарт)
Энтер.ru
KAMAZ
Lukoil
Gazprom
Tvoy Dom
Vnukovo Airlines
Norilsk Nickel
Эксист
RUSAL
Moscow Metro
Nizhpharm (STADA CIS)
Arkhangelsk Pulp and Paper Mill
JSC „Belebeevsky zavod „Avtonormal“ („BelZAN“)
Альфа Цемент

Siemens
Хохланд
ВР (БП)
EFES

—
Клиенты SAP в России

11 04 2015

Transactions

Ruslan Allgemein t-code, tcode, transaktion, tx-code, txcode 1

> Tables
> SAP FAQ

Q: Как изменить/редактировать книгу источника поставок (source list)?
A: ME0M

SM04 – Список пользователей. Позволяет просмотреть с какими транзакциями работает пользователь и сколько режимов у него открыто.
AL08 – Список активных пользователей
SM50 – Обзор процессов. В частности позволяет просмотреть работает ли ваша “зависшая» транзакция
search_sap_menu – транзакция для поиска в SAP menu

s_BCE_68001399 – узнать какие люди связаны с ролью.
S_BCE_68002041 – какие транзакции в роли.
SM01 – списки транзакций как фильтр по коду, например ввести там ME8 и смотреть какие т-коды имеют отношение к отчетам по PO

CKMM – изменение Определения цены (Price determination) или Price control indicator (S/V) (Управление ценой)
(S – надо использовать для стандартных материалов, цена – 0 руб., V – для торговых изделий)

MB1B 311 или MIGO 311 – трансфер с одного склада на другой.

VL71 – напечатать форму из поставки
VF05N – список фактур, платежных документов (например, созданных в VF01)
VF11 – сторнировать фактуру
VF31 – печать документов ко счету.
VFX3 – просмотр ошибок со счетами
MBSM – по номеру документа был ли он сторнирован?
ME2N – поиск среди закупок, список закупочных агриментов
ME2M – список закупочных документов агриментов с ценами
ME2L – поиск среди документов по поставщику. Например, если есть PO, но нет приходования MIGO, то можно вывести список, указав Document Type: NB (колонка To be delivered).
ME3L – Outline agreements per vendor
ME3M – Outline agreements per material
ME3C – Outline agreements per material group
ME3B – Outline agreements per requirement tracking number
ME3N – Outline agreements by agreement no.
MSRV5 – Service list for contract
ME3K – Outline agreements by account assignment
ME5A – вывод PR’ов с возможностью выборки лишь „полностью одобренных/деблокированных“ (Processing Status = N для тех PR’ов к которым еще нет PO).
ME9F – печать документов (в ME22N можно редактировать Message, если что-то надо печатать повторно).
ME9E – печать расписания
ME9L – печать агриментов

MF41 – сторно бэкфлаш.
MF42N – то же что и MFBF, но внесение информации о нескольких материалах подряд.
ME38 – удалить Scheduling agreement
ME55 – деблокирование заявки на закупку.
ME54N – деблокирование позиции по отдельности.
ME84 – создать call-off релизы

SU2 –
BD55 Правило преобразования для User Exit. Ссылка на правила преобразования User Exit для различных систем.

WE82 Разблокирование ссылки
WE57 Присвоение Функционального Модуля сообщению и типу IDOC

VA42 изменить контракт
VA22 Изменить предложение
VF04 обработать рабочий список фактур
VL04 рабочий список заказов клиентов/заказов на поставку
VKM3, VKM4 списки торговых документов
VKM1 блокированные документы Сбыта
VKM5 список поставок
VT02N изменение транспортировки
VT70 выходные документы к транспортировкам

Customer

XD01 Create Customer (Centrally)

XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)

Vendor

XEIP Number range maintenance: EXPIMP

XK05 Block Vendor (Centrally)
XK06 Mark vendor for deletion (centrally)
XK07 Change vendor account group

Sales Order

VA00 Initial Sales Menu
VA07 Compare Sales – Purchasing (Order)
VA08 Compare Sales – Purchasing (Org.Dt.)

Inquiry

VA11 Create Inquiry
VA12 Change Inquiry
VA13 Display Inquiry
VA14L Sales Documents Blocked for Delivery
VA15 Inquiries List

Quotation

VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA25 Quotations List
VA26 Collective Processing for Quotations

Contract

VA41 – Create Contract
VA42 Change Contract
VA42W Workflow for master contract
VA43 Display Contract
VA44 Actual Overhead: Sales Order
VA45 List of Contracts
VA46 Coll.Subseq.Processing f.Contracts

Item Proposal

VA51 Create Item Proposal
VA52 Change Item Proposal
VA53 Display Item Proposal
VA55 List of Item Proposals
VA88 Actual Settlement: Sales Orders

Deliveries

VL00 Shipping
VL01 Create Delivery
VL01N Create Outbound Dlv. with Order Ref.
VL01NO Create Outbound Dlv. w/o Order Ref.
VL02 Change Outbound Delivery
VL02N Change Outbound Delivery
VL03 Display Outbound Delivery
VL03N Display Outbound Delivery
VL04 Process Delivery Due List
VL06 Delivery Monitor
VL06C List Outbound Dlvs for Confirmation
VL06D Outbound Deliveries for Distribution
VL06F General delivery list – Outb.deliv.
VL06G List of Oubound Dlvs for Goods Issue
VL06I Inbound Delivery Monitor
VL06IC Confirmation of putaway inb. deliv.
VL06ID Inbound Deliveries for Distribution
VL06IF Selection inbound deliveries
VL06IG Inbound deliveries for goods receipt
VL06IP Inbound deliveries for putaway
VL06L Outbound Deliveries to be Loaded
VL06O Outbound Delivery Monitor
VL06P List of Outbound Dlvs for Picking
VL06T List Outbound Dlvs (Trans. Planning)
VL06U List of Uncheckd Outbound Deliveries
VL08 Confirmation of Picking Request
VL09 Cancel Goods Issue for Delivery Note
VL10 Edit User-specific Delivery List
VL10A Sales Orders Due for Delivery
VL10B Purchase Orders Due for Delivery

Pricing

V/03 Create Condition Table (SD Price)
V/04 Change Condition Table (Sales pr.)
V/05 Display Condition Table: (Sales Pr.)
V/06 Condition Categories: SD Pricing
V/07 Maintain Access (Sales Price)
V/08 Conditions: Procedure for A V
V/09 Condition Types: Account Determin.
V/10 Account Determination: Access Seqnc
V/11 Conditions: Account Determin.Proced.
V/12 Account Determination: Create Table
V/13 Account Determination: Change Table
V/14 Account Determination: Display Table

BOM

CS00 BOM Menu
CS01 Create Material BOM
CS02 Change Material BOM
CS03 Display Material BOM
CS05 Change Material BOM Group
CS06 Display Material BOM Group
CS07 Allocate Material BOM to Plant
CS08 Change Material BOM – Plant Alloc.
CS09 Display Allocations to Plant
CS11 Display BOM Level by Level
CS12 Multilevel BOM
CS13 Summarized BOM
CS14 BOM Comparison
CS15 Single-Level Where-Used List
CS20 Mass Change: Initial Screen
CS21 Mass Material Change: Initial Screen
CS22 Mass Document Change: Initial Screen
CS23 Mass Class Change: Initial Screen
CS25 Archiving for BOMs
CS26 BOM deletion
CS27 Retrieval of BOMs
CS28 Archiving for BOMs
CS31 Create class BOM
CS32 Change class BOM
CS33 Display class BOM
CS40 Create Link to Configurable Material
CS41 Change Material Config. Allocation
CS42 Display Material Config. Assignment
CS51 Create standard BOM
CS52 Change standard BOM
CS53 Display standard BOM
CS61 Create Order BOM
CS62 Change Order BOM
CS63 Display Order BOM
CS71 Create WBS BOM
CS72 Change WBS BOM
CS73 Display WBS BOM
CS74 Create multi-level WBS BOM
CS75 Change multi-level WBS BOM
CS76 Display multi-level WBS BOM
CS80 Change Documents for Material BOM
CS81 Change Documents for Standard BOM
CS82 Change documents for sales order BOM
CS83 Change documents for WBS BOM
CS84 Change documents for class BOM
CS90 Material BOM Number Ranges
CS91 Number Ranges for Standard BOMs
CS92 Number Ranges for Sales Order BOMs

10 04 2015

Smart Forms vs Adobe PDF-based forms

Ruslan ABAP, Allgemein PDF, smartforms 1

Here is a comparison between the two largest print form formats.
All new forms delivered with the ERP will be PDF-based. So, it’s probably better to get ready to change.

Knowing those two print forms possibilities offered by SAP, you want to know more about what is the best technology to use.

Hopefully I’ll provide you some answers in this paper. I’ll probably write more complete comparisons as experiences with PDF forms grows.

Smart Forms architecture

The application program retrieves data from the database and is passed to the function module generated by the Smart Form. The application program, which collects data, has to be written. In many cases, a standard print program is copied, modified and then reused.

The Smart Form needs to be defined. With transaction SMARTFORMS, you can setup the layout you want. This is a powerful but quite old tool and its usage is requires some learning time.

PDF-based print forms architecture

At runtime, we notice the architecture is very close of the previous one.

In this case, a print program also needs to be written. The PDF form template, consuming data from its interface, is called by the generated function module. The call to the web service and the PDF is physically built during runtime.

The ADS component runs on the J2EE stack and exposes a web service allowing the rendering of PDF forms. This means extra calls between both stacks.

Note that you can use this web service to build other PDF forms.

Comparison: pro et contra

Development

Every form has layout problems at some point in time. Text is too low the page; the first name is not aligned with the last name, tables don’t display correctly etc. In both cases, there are a lot of tests („chipotages“, for the French-speaking people) to perform before a form version can be released.

There is a first advantage of PDF in comparison with Smart Forms. The Adobe LiveCycle Designer (ALD) is at first sight simple, yet powerful and comprehensive. So to build a layout is easier with PDF forms for people with limited experience.

When you have lots of forms to develop, you can enhance the custom objects in the ALD: you can add multiple UI objects and group them in one element which you can easily reuse. For instance, a ‚UserData‘ element that contains firstname, lastname, street, postal code and city. Element types as well as the layout are stored locally (in folder C:\Users\\AppData\Adobe\Designer\en\objects\), so exchange with other forms developers is quick and easy.

So, bottom line is that development time can be reduced by using PDF forms. Of course, this also depends on your developers‘ skills.

Performance

As you know, every object-oriented language has performance problems. So does Java… The ADS component is also heavy and the rendering time of a very complex PDF form, with lots of scripting logic and data to display, can take some time. This may result in heavy documents. Another reason for the sometimes slow performance is the web service connection.

This performance issue must be taken into account when considering high volume printing and complex forms.

Of course, be aware there are possibilities to improve PDF rendering time. Form bundling is one of them (the bundling principle is to send multiple forms in one call to ADS); another one, valid as of NetWeaver 2004s SP12, is described in SAP Note 993612.

Smart Forms, which run fully on the ABAP side, can be faster than PDF… for the moment. I’ll probably post more about performance comparisons in the future.

Regarding stability, both technologies are equivalent and I personally never had problems regarding this. Feel free to provide your input!

Architecture

As said earlier, PDF requires a J2EE stack with ADS properly configured and with connections between both systems up and running. This is done in standard as of NetWeaver 2004 SR1 so don’t panic! Every recent SAP solution includes the J2EE stack including ADS.

There are web services calls between the ABAP and J2EE stacks, which makes for additional connections to handle.

In terms of architecture, the PDF seems to require more attention. Although, the J2EE stack with ADS is installed and configured in standard as of the ERP2004 so there should be no particular worries about this.

Front-end and clients

The PDF requires Adobe Reader to display PDF forms. Nowadays, almost every workstation has Adobe Reader installed on it. Reader is not required to print forms: hopefully, the normal PDF drivers are supported in SAP systems as well as most of standard printer drivers.

Smart Forms require no additional installations on top of the standard SAPGUI.

Compatibility

Customer examples

In this case, everything depends on your scenarios. Some examples for PDF: you need to respect a legal template, which is provided in PDF; PDF is already widely used in your company; you have all the other Adobe products; you need to send printed invoices to your customers automatically via mail with PDF format etc.

On the other hand, you can choose to use Smart Forms for various reasons: your SAP system printing documents is R/3 4.7; you have plenty of qualified developers who know Smart Forms very well; you need very high performance rather than flexibility etc.

Courses

One reference course for Smart Forms: BC470 – Form printing with SmartForms.

The Adobe LiveCycle Designer embedded in an SAP environment offers a lot of possibilities. More information can be found in SAP course BC480 – PDF based print forms (3 days).

Conclusion

Smart Forms is the faithful technology for those who know it. Still useful and reliable as well as very powerful.

On the other hand, the PDF-based print forms is highly appreciated for its comprehensiveness, compatibility, design possibilities. It’s also the future for form output in SAP solutions.

So, the choice is now yours. Personally (but as you may know, I’m not the most objective person when speaking about forms), my choice goes to the PDF for the reasons mentioned above.

29 01 2015

General SD configuration

Ruslan Customizing IMG, SD, SPRO 0

SAP SD Configuration Steps

Enterprise Structure:

Edit, Copy, Delete, Check Company Code (T001)
Company is created by FI Consultant.
The company code is an organizational unit used in accounting. It is used to structure the business organization from a financial accounting perspective.
IMG -> Enterprise Structure -> Definition -> Financial Accounting -> Define, copy, delete, check Company Code
Define Credit Control Area (T014)
Company is created by FI Consultant.
The credit control area is an organizational unit that specifies and checks a credit limit for customers.A credit control area can include one or more company codes. It is not possible to assign a company code to more than one control area. Within a credit control area, the credit limits must be specified in the same currency.
IMG -> Enterprise Structure -> Definition -> Financial Accounting-> Define Credit Control Area
Maintaining Sales Organization (TVKO)
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
Assigning Sales Organization to Company Code (TVKO-BUKRS)
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
Maintaining Distribution Channel (TVTW)
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
Assigning Distribution Channel to Sales Organization (TVKOV)
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
Maintaining Division (TSPA)
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics – General -> Define, copy, delete, check division
Assigning Division to Sales Organization (TVKOS)
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
Setting up Sales Area (TVTA)
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
Maintain sales office (TVBUR)
The definition of sales offices is optional.
For each sales office, you can determine the printer for output based on the sales documents in different ways
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Maintain Sales Office
Assign sales office to sales area (TVKBZ)
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales Office to Sales Area
Maintain sales Group (TVKGR)
The definition of sales groups is optional. You can use the SD system without creating sales groups.
Assign sales group to sales office (TVBVK)
You can assign as many sales groups as desired to the sales offices. Any one sales group can belong to several sales offices.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales group to sales office
Define Shipping Points (TVST)
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
Define, copy, delete, check plant (T001W)
Plant is created by MM Consultant.
IMG -> Enterprise Structure -> Definition -> Logistics – General -> Define, copy, delete, check plant
Assigning Sales Organization – Distribution Channel – Plant (TVKWZ)
Plant is created by MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization – distribution channel – plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
Assigning Shipping Point to Plant (TVSWZ)
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Defining Common Distribution Channels for Master Data (TVKOV-VKWKO TVKOV~VTWKU)
The purpose of this activity is to define distribution channels which have common master data. Access the activity using the following navigation:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
Defining Common Divisions for Master Data (TVKOS-SPAKO TVKOS~SPAKU)
The purpose of this activity is to define distribution channels which have common master data. Access the activity using the following navigation:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2

26 01 2015

The ways to editing tables

Ruslan BC SAP_EDIT, SE16, SE16N 0

Here are listed powerful hacks which can be used to change even the standard tables and even in a production environment (if you have CHANGE access in Debugger). You should think twice before using them.
You can track changes made in SE16N by &SAP_EDIT (GD-SAPEDIT) option in SE16N_CD_KEY table.
With a right authorization concept in place you would not be allowed to debug in production. So end users should be restricted with debugging authorizations.

1. Go to SE16N, type the table name, turn on the debugger (type /H in the command field), press F8. In the debugger set the values of GD-EDIT and GD-SAPEDIT to ‚X‘ and press F8.
2. Execute the function module SE16N_INTERFACE. Set parameters i_tab to table name and i_edit to ‚X‘ and press F8.
3. Carry out the transaction UASE16N (obsolete, but sometimes still in use). Type &SAP_EDIT in the command field.

SE16N: Abschalten von &SAP_EDIT – SAP Note 1420281

07 01 2015

LSMW upload classification

Ruslan LSMW, MM Klassifizierung, LSMW, MASS 1

On the next screen, if you press the button „Object overview“ you see next fields:

So in this case
KLART – 001 (Material Master)
OBJEK – material master number
CLASS – Class name
ATNAM – Characteristic name
ATWRT – Characteristic value

Save it.

Specify files:

Window of „Start direct input program“:

If no error, you will see the deliberate error (that was added in last line)

After loading it in, you can verify the data in the table AUSP where class type = 001:

27 12 2014

Working with the Material Master Data

Ruslan SAP ECC 6.0, Master data, MM 2

In the SAP MM module, material master data refers to all the material master records that are stored in the system. In other words, material master data consists of the description of all the materials that an organization not only purchases but also produces and keeps in its stock. The material master data acts as a central database of information for the materials in an organization.

Maintaining the details of all the materials at a central location not only minimizes the risk of data redundancy but also allows other departments of the organization to share this data among themselves. The other departments of the organization can use the material master data to perform various tasks, such as invoice verification and inventory management. The material master record is used by different departments of an organization, and each department requires different information about the material. For example, the purchasing department might require only the price of the material to perform price control functions; whereas, the sales department might require the sales data to prepare the sales graph of a given period of time.

To facilitate locating the relevant data, various fields have been provided in the Create Material (Initial Screen). Every department can easily locate and access the data required by it by entering the relevant details in these fields.
More

22 12 2014

Quiz for SD (TSCM60)

Ruslan Allgemein Quiz, TSCM60 0

Attached are four pdf documents with sample questions and answers that can be of use when you do you SAP Sales and Distribution Certification exam:

quiz

Quiz TSCM60 set A questions.pdf
Quiz TSCM60 set A answers.pdf
Quiz TSCM60 set B questions.pdf
Quiz TSCM60 set B answers.pdf

18 12 2014

What are Enjoy transactions in SAP?

Ruslan SAP Enjoy, MCV9 1

sap_enjoy

An enjoy transaction is one that was released with the mysap.com release, which is also know as the „Enjoy“ release.
Enjoy transactions are the new transactions (from rel. 4.6A, which is nearly 10 years old now) were created to „make life easier“ for the endusers and performs all the operations performed by its classical counterpart in one screen only. All clickable elements have 3D qualities, while the input and output fields remain 2D for simplified reading.
A lot of transactions have been rewritten to use the new control framework. All Enjoy transactions are having ‚N‘ character at the suffix of the transaction (ME21N, VL02N etc). These transactions „replaced“ older transactions. The sap enjoy transactions typically are much more user friendly in appearance, support custom controls, ALV tree and ALV grids, docking containers, node structures, picture controls in them. But transactions ending with „N“ doesn’t qualify them as eNjoy. May be „N“ was used to indicate „New“, SE43 & SE43N – neither of them are eNjoy transactions.

sap-enjoy

As example described data can be found in the t-code ME21N (completely writting in OOPS ABAP). The old ME21 transaction uses the classic dynpro technology without using the control framework.
Enjoy sap controls are containers that can built dunamically using objects/classes. In general batch input is not possible for those screens. The SAP material BC412 contains all about this. It’s all about ABAP Screen programming.

Today the term „Enjoy“ is not common anymore.

„SAP software works the way I do.“

P.S. MCV9 transaction:

MCV9

«< 2 3 4 5 6 >»