Step-by-step procedure to enter condition record?
Hi ,
Could someone please explain the step-by-step procedure to enter condtion record for pricing when creating a sales order?
Hello,
Please refer to the SAP online help; this is not a subject for the Abap forum.
Regards,
John.
Similar Messages
-
Is any SD/MM Configuration step by step procedure available in the market?
Dear fellow SDN's,
Please give me a guide on
1. Where to start SD learning?
2. How to proceed to become a strong SD consultant.
3. Is any SD/MM configuration procedure pdf / Document available in the market?
I have an ECC 6.0 remote connectivity.
Your valuable advice appreciated and allow to earn good credit.
Thanks in advance.
Regards.HI Stockton,
1. Try to start with the Basic Concepts of SD which are given Below:
SD FLOW/ OVERVIEW:
Sales
Inquiry - A customers request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.
Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.
Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.
The sales area that accepts the inquiry is responsible for completing the agreement.
Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.
b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).
c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.
Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.
Sales Order Management Transactions
SALES ORDER PROCESSING
Creating Sales Order - VA01
Maintaining a Sales Order - VA02
Displaying a Sales Order - VA03
Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1
Display List of RMAs by Customer - VA05
Confirm RMA Goods Receipt - VL02
Generate list of open return orders for deletion - VA05
Display Customer returns eligibility - MCSI
Removing a Billing Block (Approving Credit/Debit Requests) - V.23
PRICING MASTER DATA
Create Pricing - VK11
Creating a Sales Deal - VB21
Maintaining a Sales Deal - VB22
Displaying a Sales Deal - VB23
Maintaining Prices - VK12
Displaying Prices - VK13
MATERIAL MASTER DATA
Creating Material Substitution Master Data - VB11
Maintaining/Deleting Material Substitution Master Data - VB12
Displaying Material Substitution Master Data - VB13
Creating a Bundled Master - MM01
Creating a Sales BOM - CS01
Maintaining a Sales BOM - CS02
Displaying a Sales BOM - CS03
CUSTOMER MASTER DATA
Creating Partner Records - XD01
Maintaining Customer Master Data - XD02
Displaying Customer Master Data - XD03
Deactivating a Partner - VD06
CUSTOMER CREDIT INFO
Creating/Maintaining New Customer Credit Information - FD32
Displaying Customer Credit Information - FD33
Blocking or Unblocking a Customer - VD05
SHIPPING
Creating a Delivery - VL01N
Displaying a Delivery - VL03N
Changing a Delivery - VL02N
Shipment Inquiry / Display - VT03
Adjusting Transfer Order - Confirmation Quantity - LT12
Collectively Confirm Transfer Order - LT25
Batch Shipment Confirmation - VL19
PGI Reversal Cancellation - VL09
Creating Service Provider/Carrier Master Data - XK01
Maintaining Serive Provider/Carrier Master Data - XK02
Displaying Service Provider/Carrier Master Data - XK03
Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02
IDoc Inquiry - WE02 / WE05
BILLING
Invoicing a Customer Shipment - VF01
Reprinting an Invoice - VF31
Releasing a Sales Order for Billing - V.23
Creating an Invoice by Using the Billing Due List - VF04
Checking Open Billing Documents - VF05
Create Credit/Debit Memo - FB01
A/R
Controlling Total Debit/Credit bkgs - F.03
Generate FI Account balance - F.08
Generate Month-to-date Inv. register - F.02
Process payments - FBZ1
Rqst Individual Customer Corresp. - FB12
Generate Customer Correspondence - F.61
Enter Batch totals under Control ttl - FB07
Display G/L Acct. totals - FBL3N
Reverse Posted Amounts - FB08
Customer Refunds - FBL6
Customer Refund to other than Payer - FB05
Clearing Debit/Credit on Cust. acct. - FB1D
Customer Balance in Local Currency - F.23
G/L Account Balance Report - F.08
Create Invoice - legal entity adjust - FB01
Generate Cust. Acct. statements - F.27
Generate Dunning Letters - F150
Generate Billing Due List - VF04
Generate Blocked Billing Doc list - VFX3
Inq. via Credit Release Screen - VKM1
List orders by partner - VA05
Past Due invoices by customer - FD11
Check number info by G/L account - FBL3N
Display customer Line items - FBL5N
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
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
2. Assigning Sales Organization to Company Code
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
3. Maintaining Distribution Channel
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
4. Assigning Distribution Channel to Sales Organization
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
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
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
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
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
10 Assigning Shipping Point to Plant
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
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
he configuration differs from scenario to scenario & requirement of the client.
Interesting &important link to learn much more about configuration & business process is as under:
Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on.
SD FLOW
SD Flow Cycle:
INQUIRY ( VA11)
|
QUOTATION (VA21)
|
PURCHASE ORDER (ME21)
|
ORDER CONFIRMATION (VA01)
|
PICKING LIST (VL36)
|
PACKING LIST - (VL02, VL01)
|
SHIPPING (VT01)
|
INVOICE (VF21, VF01)
|
AR
2.Hope aware that SAP- SD itself the Big one.try to Explore the various Scenarios in SD and be Stong in Some Areas like Pricing, Intercompany Billing, Third Party Sales, LSWM, EDI Etc.,
3.The link between SD and MM: -
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availability check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order, the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
SD INTEGRATON WITH MM
1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availability check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order, the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM
In Pricing we would want to determine the cost of the product
thru VPRS Condition Type. This cost of the material is
picked from the Material Master. How this happens is, if
we would want to determine this cost VPRS in the Sales Order
for Profitability purpose then , all those Item categories
that can appear in a sales order must be activated for
Determine Cost Check box in customizing. Thats one of the SD
MM Integration.
Please go through the below Link,
http://sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
Hope Clarifies your doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Pricing condition records should not be picked up
Hi,
I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
Do I have to use any Userexits, if so which one?
Regards,
AbhishekAs mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
To configure new Document Pricing Procedure:
IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
Pricing Procedure Determination:
In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Pricing Procedure Configuration:
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka -
What is the Procedure to Create "Condition Value" Routine Using VOFM
Dear Guru,
I want to know Step-By-Step Procedure to Create "Condition Value" Routine Using VOFM.
Give me guideline how it will link to program RV64ANNN.
and if it doesnot link to RV64ANNN
what might be the possible reason and how to make it link with RV64ANNN.Dear Guru.
I have encountered a technical issue related to Creation of User Routine for pricing procedure
(Routine :: RV64A978).
Before coming to issue I want to give you slight glance on my requirement.
I have got two requirements to write two routines for a new condition type -->> packing type .
>>Routine Number One First I Have wrote Requirement Routine RV61A943
Routine Number two Other I Have wrote calculate condition value RV64A978
So as usual normal procedure of writing a routine I followed VOFM for writing routine for pricing procedure and routine for calculation (condition value).
I performed above respective process for both routines in VOFM.
And I have activated both routine from going VOFMMenu bar edit Activate.
After activation automatic include is generated in both case .
INCLUDE RV61A943 . "FAMD PAckage Wt
Is generated in RV61ANNN
INCLUDE RV64A978 . "FAMD Package-Rate
Is generated in RV64ANNN
In case of Routine RV61A943
I can able to find the main include routine RV61ANNN from where used function in SE38 and able to trace it.
And I am able to find it in the lists of Includes of RV61ANNN.
But In case of Routine RV64A978
I can not able to find the main include routine RV64ANNN from where used function and able to trace it. Pls refer below picture.
But in RV64ANNN it is showing that routine RV64A978 is there
So Guru I want to know following things >
1. What might be the main reason in case of RV64A978 ??
2. How I should approach to solve this issue??
Because what I understood unless routine RV64A978 is traceable from u201Cwhere usedu201D to find out its main routine RV64ANNN , the routine RV64A978 wont work in pricing procedure (I believe). -
Condition records for Plant/SLocation - output determination
Is there any BAPI for uploading the condition records in OMJ3?
This is for entering condition records in inventory management based on plant/SLoc parameters.
pls advice
Thanks.I am not aware of any BAPI, but you can try using a BDC Program or LSMW to upload these.
RJ -
Condition Records For Tax Condition types for SAP 4.7
Dear Experts,
What is the procedure to maintain condition records for tax condition types like CST , VAT and Service Tax. We are not using CIN. In MM01 and XD02 tax classifications i have maintained UTXJ condition Type and also maintained the above mention tax condition types.. But when i create condition records for UTXJ in VK11 the sysytem is asking for Tax code. In FTXP when i defined Tax code A1 for Tax ProcedureTAXIN1 where i maintained all the Tax condition types there.But i am unable to save the Tax % in FTXP.When i try to save the tax code it is not saving.
Is there any other procedure to maintain Tax condition types for SAP4.7.
My Pricing procedure that i maintained in V/08 is Z00001.
Regards
JyotiHi Jyoti
Since you are not using CIN, you can do the follwing for tax conditions
Check the assignment of the TAx procedure to country
once u do this , you will be able to maintin the vendor and customer records for MWST type for taxes
then create condition records for MWSt with access sequence MWST in condiution type or design one suited to your needs
alternatevely in the current procedure you can change access sequence for condition type UTXJ form the current one to MWST and then maintain condition records
hope this helps
thanks
Akasha -
Tax classification Condition records details in FV11
Hello All
We are using the TAXINN procedure & mainatining the condition records by tax clasiification
by maintaining the tax code in FTXP & define all your condition value for the same tax code ( JMOP ( Excise Duty ), JEC1 ( Education Cess , JSEP ( Higher Education cess ) & set off condition JMX1,JEX1, JHX1 respectively
but in tax clasification in FV1 if we first maintain the condition JMOP excise duty for the tax code Z1 as 8% & after that when we are going for maintain the JEC1 for TAX CODE Z1 as 2%
it is giving error that for Z1 8 % IS ALREADY EXIST
But if we mainatin the set off condition JMX1,JEX1, JHX1 100 % first & then maintaining the JMOP, JEC1 & JSEP system is not giving error
Please suggest
Regards
RajeshFrom OBQ1 , check the access sequence of each of the CIN condition types . eg: JTAX.
In OBQ2, for the access sequence ,see the tabe names /numbers of each of the key combination tables. eg: 363 -Plant/Vendor/Material
To get the SAP table name of Table 363, just add "A" before it. so Table A363 stores the details of combination Plant/Vendor/Material .
Now, the Table A363 does not store the actual values (%) of the records, it stores the validity period., to get the Actual values, take the condition record field from A363 and pass it to KONP , KONP will give you the actual rates of the condition records. -
Service Tax - Key Combination to Maintain Condition Record
Dear Experts,
Can anybody please explain which Key Combination is to be selected while maintaining Condition record for Service Tax ( 0% service tax and Service tax 12.5 + ECS).
I have created two tax codes - S1 and S0. please explain the procedure to maintain condition record for Service Tax.
Thanks in Advance.HI,
TAXINN is condition based. The functionality does not work with tax codes, tax codes are for informative purpose..
JMX1 can be maintained in FV11 with the help of a key combination.
When you create this condition with respect to vendor/material combination then when a PO is made with these 2 combination the system gets the percentage / value from the condition record and calculates the price.
Thanks & Regards,
Kiran -
Reg Maintanance of GR Message We03 condition record
When i try to enter condition record for WE03[ GR] its only appearing in MN21, it is not in NACE > ME> condition records , why is that. Where i find MN21 in SAP tree?
Please helpUse transaction SE16 or SE16N and have a look at table NACH.
Cheers,
Nick -
499 Step Number for condition record?
Hello Everyone,
In ECC6, Quotation print output AN00 is not showing price per unit for some items. I checked in debug, there seem to be a condition record with step number 499 (which does not have a condition type) that is missing values for XKOMV-KBERT. When I populate this value in debug, it shows up find in the output. Step number 499 is not in KONV. What logic does SAP use to come up with these values for step number 499?
I know this may sound like an ABAP question but it is not. I think some pricing is not configured right. There is a calculation type condition but it is only populating field KWERT.
TIA,
LynHi lyn
Check in your piricing procedure V/08 wheather , in the step 499 what has been maintained any text type ? and if condition type has been maintained. , check wheather condition record has been maintained or not ? and also check wheather that value is coming in the sales order or not .
check for the step 499 wheather in print feild it has been checked or not .
Regards
Srinath -
Step for Adding new condition in Pricing procedure
Hi,
We have different pricing procedure with different condition , in this procerdure i want to add one new condition at 2 position and the requirement is that if system found the value with this condition it should skip the 3 step and directly go to 4 step can u give the step for this how to add new condition to this procedure.
regards,
zafarI think you need to use condition exclusion so if the condition at step 2 is found then step 3 becomes inactive if it is also found.
Depnding on your pricing keys, you might be able to add a step in the access sequence on step 3 and only use a single condition (V/07) and marking that step exclusive if a record is found. -
Steps to maintain condition records for MB1B
Hi all,
i need complete steps to maintain condition records for
T Code MB1B for stock transfer between storage locations for same plant with movement type 311
Your help will be appreciated
SiddharthHi Siddharth,
TP b/w st.locs of same plant there wont be any accounting documents generated..so ..no condition records required.....as such,,material will be in plant only...means same valuation area..
Check the basic rules.....
BR,
Krishna -
Pricing Procedure and automatic triggering of condition records
Dear Gurus,
I am a junior SAP SD consultant.
At the moment I am customizing SAP to generate sales documents and am using a standard pricing procedure called: RVAA01
At T-Code: V/08 when you access the reference steps of that pricing procedure you see a lot of steps ranging from
step 8 to 971
At sales order level VA01, once you have entered a PR00 condition record in VK11, and you click to view the pricing procedure:
- Why does the system only selected those basic conditions and not more?
PR00
AZWR
MWST
SKTO
VPRS
- How does the automatic selection process occur in the pricing procedure to have hundreds of steps ready to use to finally come down to those 5 steps at sales order level?
Your help is greatly needed
Regards
ChrisWhatever condition types you see in pricing procedure the same will be in V/06 where you can also see three fields
a) Access Sequence
b) Header condition and
c) Item condition
All your condition types that flows into your sale order will depend on these settings.
Normally, all item condition types will have access sequence assigned on top right for which, you will have to have relevant tables assigned in V/07.
Whatever tables you maintain in V/07, based on this combination, you would be maintaining pricing in VK11 for that condition type.
Based on the above settings, when you create a sale order, system will search for the required combination and fetch the pricing. This is for item level condition type.
For header condition type, you will not be having access sequence assigned in V/06. You can key in manually in sale order at header level condition tab so that the corresponding value will be bifurcated equally to all line items.
thanks
G. Lakshmipathi -
Pricing step by step procedure
Dear Experts,
pls send me the pricing notes ( step by step procedures) at my mail id
[email protected]
always reward point ...
Thanks b4 hand
VaibhavHi Vaibhav,
Following are the steps you need to follow for pricing.
Reward if this helps you...
PRICING (PG)
This concept is based on condition technique.
Its the combination of:
1) Condition Tables
2) Access Sequence
3) Condition Types
4) Pricing Procedure
1. Condition Tables: - Condition table contain the key fields for maintaining condition records. I.e. in other words condition records are stored in condition table.
Note: - A condition type can have multiple condition tables.
Note: - A condition table can be used for multiple condition types.
Defining condition tables: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition tables [V/03]
Create condition tables
Enter a table number beyond 600
From the field catalogue, which is there on the right side of the screen select the required key fields.
To get the valid on / valid to fields while maintaining the condition records we need to check the field with validity period.
Go to icon Technical View
The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
Select the Icon Generate for generating the condition table.
To save the condition table, select the button Local object.
2. Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records. It contains the required condition tables in the required order.
Note: - If required an access sequence can be used or assigned to multiple
Condition types.
Note: - The order in which the condition table are placed in access sequence
is important generally it is most specific to most generic
Defining Access Sequence: -
SPRO
Sales and distribution
Basic functions
Pricing
Pricing control
Define access sequences
Maintain access sequences
Go to new entries and define the access sequence.
Select the defined access sequence and go to accesses.
Go to new entries and place the condition tables in the required order
While placing the condition tables check the field exclusive. By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
Select the condition table and go to fields the system gives the warning message the field assignment has not yet been made say enter till we get the fields.
Repeat the same step for all the condition tables and save it.
Note: - After defining the access sequence assign it to the corresponding condition type.
3. Condition Types: -
Defining condition types: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition types.
Maintain condition types.
Functionality of a condition type: -
Access Sequence: - In this field specify the corresponding access sequence for the condition type.
Condition class: - It is the preliminary structuring of condition types.
Ex: - Surcharges or discounts and price
Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
Condition Category: - Its a classification of conditions according to pre-defined categories.
Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
Delete: - If we check this field the condition type can be deleted during the sales document processing.
Value: - If we check this field the condition value can be changed during the document processing.
Calculation type: - If we check this field the calculation type can be change during the document processing.
Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
Ex: - RB00 (Discount).
Note: - After entering the header condition type click on the button activate.
Note: - The condition amount of the header condition is copied as it is to all the line items in the document
Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
Note: - Header condition wont be having access sequence.
4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.
Defining Pricing Procedure: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define and assign pricing procedures.
Maintain pricing procedures
Go to new entries and define the pricing procedure.
Select the defined pricing procedure and go to control data
Go to new entries and place the required condition type in a specified order.
Step: - Specifies the number that determines the sequence of a condition type with in a procedure.
Counter: - Specifies the sequence number of a condition type with in a step in the procedure.
Condition type: - Specify the condition type.
From & To: - If you specify the reference steps in these fields, the condition values of the two steps specified and the condition values of the steps in between are totaled.
Manual: - If we check this field the condition type is only included in determination either if they are entered manually or if they are transferred from an external process such as costing.
Mandatory: - Indicates whether a condition type is mandatory when the system carries out pricing using the pricing procedure.
Statistical: - This indicator causes a condition type to be set in the document statistically only.
Print ID: - Controls the issue of condition lines when printing the documents such as order conformations or invoices. [X]
Sub Total: - Controls whether and in which fields the condition amounts or subtotals are stored.
Requirement: - For the condition type to be executed in the sales document the requirement specified here must be satisfied. [2]
Alternative calculation type: - Specifies the alternative formula to the calculation type in the standard system that determines a condition.
Alternative condition base value: - Specifies the formula for determining the condition basis as an alternative to the standard.
Account key: - This field along with few other fields enables the system to post the sales values to different General Ledger Accounts.
Ex: -
ERL  Sales Revenues
ERS  Sales Deductions
ERF  Freight Revenue
Accruals: - This is exclusively for rebate condition types. [B001 & B002]
Key, which identifies various types of General Ledger accounts for accruals posting.
Note: - to maintain the requirements and routines use the transaction code
[VOFM]
Pricing Procedure Determination: -
SPRO
Sales and Distribution
Basic Functions
Pricing
Pricing control
Define and Assign Pricing Procedures.
Define Pricing procedure determination [OVKK]
We have to assign the pricing procedure to the combination of Sales Organisation, Distribution Channel, Division, Document Pricing Procedure and customer pricing procedure.
Sales Organisations Distribution Channels Divisions Doc. Pricing Procedure Cus. Pricing Procedure
1000 10 00 A 01 & 02
2000 12 00 A 01 & 02 -
Pls Send me Step by Step procedure for a Smartforms
hi all ,
pls send me Step by step procedure for a Smartform creation or PPT to This Email id : [removed by moderator]
thanks in advance
rgds
rafi.vhi mahammad rafi,
u can read this,
smart forms
Introduction to SAP SmartForms
What is SAP Smart Forms?
SAP Smart Forms is introduced in SAP Basis Release 4.6C as the tool for creating and maintaining forms.
SAP Smart Forms allow you to execute simple modifications to the form and in the form logic by using simple graphical tools; in 90% of all
cases, this won't include any programming effort. Thus, a power user without any programming knowledge can
configure forms with data from an SAP System for the relevant business processes.
To print a form, you need a program for data retrieval and a Smart Form that contains the entire from logic. As data retrieval and form logic
are separated, you must only adapt the Smart Form if changes to the form logic are necessary. The application program passes the data via
a function module interface to the Smart Form. When activating the Smart Form, the system automatically generates a function module. At
runtime, the system processes this function module.
You can insert static and dynamic tables. This includes line feeds in individual table cells, triggering events for table headings and subtotals,
and sorting data before output.
You can check individual nodes as well as the entire form and find any existing errors in the tree structure. The data flow analysis checks
whether all fields (variables) have a defined value at the moment they are displayed.
SAP Smart Forms allow you to include graphics, which you can display either as part of the form or as background graphics. You use
background graphics to copy the layout of an existing (scanned) form or to lend forms a company-specific look. During printout, you can
suppress the background graphic, if desired.
SAP Smart Forms also support postage optimizing.
Also read SAP Note No. 168368 - Smart Forms: New form tool in Release 4.6C
What Transaction to start SAP Smart Forms?
Execute transaction SMARTFORMS to start SAP Smart Forms.
Key Benefits of SAP Smart Forms:
SAP Smart Forms allows you to reduce considerably the implementation costs of mySAP.com solutions since forms can be adjusted in
minimum time.
You design a form using the graphical Form Painter and the graphical Table Painter. The form logic is represented by a hierarchy structure
(tree structure) that consists of individual nodes, such as nodes for global settings, nodes for texts, nodes for output tables, or nodes for
graphics.
To make changes, use Drag & Drop, Copy & Paste, and select different attributes.
These actions do not include writing of coding lines or using a Script language.
Using your form description maintained in the Form Builder, Smart Forms generates a function module that encapsulates layout, content
and form logic. So you do not need a group of function modules to print a form, but only one.
For Web publishing, the system provides a generated XML output of the processed form.
Smart Forms provides a data stream called XML for Smart Forms (XSF) to allow the use of 3rd party printing tools. XSF passes form content
from R/3 to an external product without passing any layout information about the Smart Form.
Advantages of SAP Smart Forms
SAP Smart Forms have the following advantages:
1. The adaption of forms is supported to a large extent by graphic tools for layout and logic, so that no programming knowledge is
necessary (at least 90% of all adjustments). Therefore, power user forms can also make configurations for your business processes with
data from an SAP system. Consultants are only required in special cases.
2. Displaying table structures (dynamic framing of texts)
3. Output of background graphics, for form design in particular the use of templates which were scanned.
4. Colored output of texts
5. User-friendly and integrated Form Painter for the graphical design of forms
6. Graphical Table Painter for drawing tables
7. Reusing Font and paragraph formats in forms (Smart Styles)
8. Data interface in XML format (XML for Smart Forms, in short XSF)
9. Form translation is supported by standard translation tools
10. Flexible reuse of text modules
11. HTML output of forms (Basis release 6.10)
12. Interactive Web forms with input fields, pushbuttons, radio buttons, etc. (Basis-Release 6.10)
A Simple Smartform Tutorial
SAP Smartforms can be used for creating and maintaining forms for mass printing in SAP Systems. The output medium for Smartforms
support printer, fax, e-mail, or the Internet (by using the generated XML output).
According to SAP, you need neither have any programming knowledge nor use a Script language to adapt standard forms. However, basic
ABAP programming skills are required only in special cases (for example, to call a function module you created or for complex and extensive
conditions).
1. Create a new smartforms
Transaction code SMARTFORMS
Create new smartforms call ZSMART
2. Define looping process for internal table
Pages and windows
First Page -> Header Window (Cursor at First Page then click Edit -> Node -> Create)
Here, you can specify your title and page numbering
&SFSY-PAGE& (Page 1) of &SFSY-FORMPAGES(Z4.0)& (Total Page)
Main windows -> TABLE -> DATA
In the Loop section, tick Internal table and fill in
ITAB1 (table in ABAP SMARTFORM calling function) INTO ITAB2
3. Define table in smartforms
Global settings :
Form interface
Variable name Type assignment Reference type
ITAB1 TYPE Table Structure
Global definitions
Variable name Type assignment Reference type
ITAB2 TYPE Table Structure
4. To display the data in the form
Make used of the Table Painter and declare the Line Type in Tabstrips Table
e.g. HD_GEN for printing header details,
IT_GEN for printing data details.
You have to specify the Line Type in your Text elements in the Tabstrips Output options.
Tick the New Line and specify the Line Type for outputting the data.
Declare your output fields in Text elements
Tabstrips - Output Options
For different fonts use this Style : IDWTCERTSTYLE
For Quantity or Amout you can used this variable &GS_ITAB-AMOUNT(12.2)&
5. Calling SMARTFORMS from your ABAP program
REPORT ZSMARTFORM.
Calling SMARTFORMS from your ABAP program.
Collecting all the table data in your program, and pass once to SMARTFORMS
SMARTFORMS
Declare your table type in :-
Global Settings -> Form Interface
Global Definintions -> Global Data
Main Window -> Table -> DATA
Written by : SAP Hints and Tips on Configuration and ABAP/4 Programming
http://sapr3.tripod.com
TABLES: MKPF.
DATA: FM_NAME TYPE RS38L_FNAM.
DATA: BEGIN OF INT_MKPF OCCURS 0.
INCLUDE STRUCTURE MKPF.
DATA: END OF INT_MKPF.
SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
MOVE-CORRESPONDING MKPF TO INT_MKPF.
APPEND INT_MKPF.
ENDSELECT.
At the end of your program.
Passing data to SMARTFORMS
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
formname = 'ZSMARTFORM'
VARIANT = ' '
DIRECT_CALL = ' '
IMPORTING
FM_NAME = FM_NAME
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
if sy-subrc <> 0.
WRITE: / 'ERROR 1'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function FM_NAME
EXPORTING
ARCHIVE_INDEX =
ARCHIVE_INDEX_TAB =
ARCHIVE_PARAMETERS =
CONTROL_PARAMETERS =
MAIL_APPL_OBJ =
MAIL_RECIPIENT =
MAIL_SENDER =
OUTPUT_OPTIONS =
USER_SETTINGS = 'X'
IMPORTING
DOCUMENT_OUTPUT_INFO =
JOB_OUTPUT_INFO =
JOB_OUTPUT_OPTIONS =
TABLES
GS_MKPF = INT_MKPF
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Additional Fonts for your SMARTFORMS
You can create additional fonts and style with transaction SMARTSTYLES
This can then be define in the paragraph and character formats, which you can then be assign to texts and fields in the Smart Form.
The character formats includes effects such as superscript, subscript, barcode and font attributes.
Difference with SMARTFORMS vs. SapScript(SE71)
The Following are the differences :-
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Labels cannot be created in smartforms.
d) Routines can be written in smartforms tool.
e) Smartforms generates a function module when activated.
Contributed by : SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips
f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format.
In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are
working in CRM 3.0 environment.
In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a
particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to
create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up
the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is
printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is
something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
FAQ on Migrating SAPscript to SmartForms
Is it possible to migrate a SAPscript form to a Smart Form?
Smart Forms provides a migration tool for this purpose which migrates layout and texts of a SAPscript form to a Smart Form. It does not
migrate SAPscript form logic of the print program. Using Smart Forms, this logic is described by the tree structure of the Form Builder. The
effort involved in migrating it depends on the complexity of the print program.
Which Basis Release do I need to use SAP Smart Forms?
SAP Smart Forms is available as of R/3 Basis Release 4.6C.
I have heard that Smart Forms replaces SAPscript. What does "replace" mean?
It does not mean that SAPscript is removed from the Basis shipment. Even as of Basis Release 4.6C, SAPscript remains part of the SAP
standard and there are no plans to remove it. Since Smart Forms is currently, and will continue to be, the tool for form maintenance for
mySAP.com solutions, our further development efforts will focus on Smart Forms, not on SAPscript.
Do we have to migrate all SAPscript forms to Smart Forms?
There is no point in migrating all SAPscript forms already in use. Since SAPscript can still be used and will be available in the future, there is
no need to. If you plan to migrate a SAPscript form, it is recommended that you check whether benefit is worth the effort involved.
Conversion of SAPSCRIPT to SMARTFORMS
SAP provides a conversion for SAPscript documents to SMARTforms.
This is basically a function module, called FB_MIGRATE_FORM. You can start this function module by hand (via SE37), or create a small ABAP
which migrates all SAPscript forms automatically.
You can also do this one-by-one in transaction SMARTFORMS, under
Utilities -> Migrate SAPscript form.
You could also write a small batch program calling transaction SMARTFORMS and running the migration tool.
SmartForms System Fields
Within a form you can use the field string SFSY with its system fields. During form processing the system replaces these fields with the
corresponding values. The field values come from the SAP System or are results of the processing.
System fields of Smart Forms
&SFSY-DATE&
Displays the date. You determine the display format in the user master record.
&SFSY-TIME&
Displays the time of day in the form HH:MM:SS.
&SFSY-PAGE&
Inserts the number of the current print page into the text. You determine the format of the page number (for example, Arabic, numeric) in
the page node.
&SFSY-FORMPAGES&
Displays the total number of pages for the currently processed form. This allows you to include texts such as'Page x of y' into your output.
&SFSY-JOBPAGES&
Contains the total page number of all forms in the currently processed print request.
&SFSY-WINDOWNAME&
Contains the name of the current window (string in the Window field)
&SFSY-PAGENAME&
Contains the name of the current page (string in the Page field)
&SFSY-PAGEBREAK&
Is set to 'X' after a page break (either automatic [Page 7] or command-controlled [Page 46])
&SFSY-MAINEND&
Is set as soon as processing of the main window on the current page ends
&SFSY-EXCEPTION&
Contains the name of the raised exception. You must trigger your own exceptions, which you defined in the form interface, using the
user_exception macro (syntax: user_exception <exception name >).
Example Forms Available in Standard SAP R/3
SF_EXAMPLE_01
Simple example; invoice with table output of flight booking for one customer
SF_EXAMPLE_02
Similar to SF_EXAMPLE_01 but with subtotals
SF_EXAMPLE_03
Similar to SF_EXAMPLE_02, whereby several customers are selected in the application program; the form is called for each customer and all
form outputs are included in an output request
Smart forms Frequently Asked Questions
Forcing a page break within table loop
Create a loop around the table. Put a Command node before the table in the loop that forces a NEWPAGE on whatever condition you want.
Then only loop through a subset of the internal table (based on the conditions in the Command node) of the elements in the Table node.
Font style and Font size
Goto Transaction SMARTSTYLES.
There you can create Paragraph formats etc just like in sapscript.
Then in your window under OUTPUT OPTIONS you include this SMARTSTYLE and use the Paragraph and character formats.
Line in Smartform
Either you can use a window that takes up the width of your page and only has a height of 1 mm.
Then you put a frame around it (in window output options).
Thus you have drawn a box but it looks like a line.
Or you can just draw "__" accross the page and play with the fonts so that it joins each UNDER_SCORE.
Difference between 'forminterface' and 'global definitions' in global settings of smart forms
The Difference is as follows.
To put it very simply:
Form Interface is where you declare what must be passed in and out of the smartform (in from the print program to the smartform and out
from the smartform to the print program).
Global defs. is where you declare data to be used within the smartform on a global scope.
ie: anything you declare here can be used in any other node in the form.
Smartforms function module name
Once you have activated the smartform, go to the environment -> function module name. There you can get the name of funtion module
name.
The key thing is the program that calls it. for instance, the invoice SMARTFORM LB_BIL_INVOICE is ran by the program RLB_INVOICE.
This program uses another FM to determine the name of the FM to use itself. The key thing is that when it calls this FM (using a variable to
store the actual name), that the parameters match the paramters in your smartform.
Another thing to note is that the FM name will change wherever the SF is transported to.
So you need to use the FM to determine the name of the SF.
Here is the code that can be use to determine the internal name of the function module:
Code:
if sf_label(1) <> '/'. " need to resolve by name
move sf_label to externalname.
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
formname = externalname
importing
fm_name = internalname
exceptions
no_form = 1
no_function_module = 2
others = 3.
if sy-subrc <> 0.
message 'e427'.
endif.
move internalname to sf_label.
endif.
It checks to see if the sf_label starts with a '/', which is how the internal names start. if it does, the name has already been converted. If
not, it calls the FM and converts the name.
You would then CALL FUNCTION sf_label.
Smartforms FAQ Part Two
Smartforms output difference
Problem with Smartforms: in a certain form for two differently configured printers, there seem to be a difference in the output of characters
per inch (the distance between characters which gives a layout problem - text in two lines instead of one.
It happens when the two printers having different Printer Controls' if you go to SPAD Menu (Spool Administrator Menu) you can see the
difference in the Printer Control and if you make the Printer control setting for both the printers as same. then it will be ok. and also u have
to check what is the device type used for both the output devices.
SmartForms Output to PDF
There is a way to download smartform in PDF format.
Please do the following:
1. Print the smartform to the spool.
2. Note the spool number.
3. Download a PDF file (Acrobat Reader) version of the spool by running Program RSTXPDFT4 and entering the
noted spool number.
SmartForm Doublesided printing question
Your customer wants your PO SmartForm to be able to print "Terms and Conditinos" on the back side of each page. They don't want to
purchase pre-printed forms with the company's logo on the front and terms & conditions on the back. Now this presents an interesting
problem.
Has anyone else ever had a request like this? If for example there was a 3 page PO to be printed, they want 3 pieces of paper, the front
side of each to containe the PO information (page 1, 2, and 3) and the back side of each piece of paper to containg the static "Terms &
Conditions" information.
Anyone have a clue how to force this out?
Easy - page FRONT lists page CONTACTS as next page and CONTACTS lists FRONT as next page. Since CONTACTS does not contain a MAIN
window, it will print the contacts info and then continue on to FRONT for the rest of the main items. Additionally, set print mode on FRONT to
D (duplex) and set CONTACTS to 'blank' (for both resource name and print mode - this is the only way to get to the back of the page).
Transport Smart Forms
How does one transport SMARTFORM? SE01?
How do you make sure that both, the SMARTFORM & it's function module gets transported? Or does the FM with same name gets generated
automatically in the transported client?
A smartform is transported no differently than any other object. if it is assigned to a development class that is atteched to a transport layer,
it will be transported.
The definition is transported, and when called, the function module is regenerated.
This leads to an interetsing situation. On the new machine, it is very likely the function module name will be different than the name on the
source system. Make sure, before you call the function module, you resolve the external name to the internal name using the
'SSF_FUNCTION_MODULE_NAME' function module.
Typically, generate the SF, then use the pattern to being in the interface. Then change the call function to use the name you get back from
the above function module.
Smartforms: protect lines in main window.
How to protect lines in the main window from splitting between pages?
It was easy with SAPscript, but how to do it with SF's. For 4.7 version if you are using tables, there are two options for protection against
line break:
- You can protect a line type against page break.
- You can protect several table lines against page break for output in the main area.
Protection against page break for line types
- Double-click on your table node and choose the Table tab page.
- Switch to the detail view by choosing the Details pushbutton.
- Set the Protection against page break checkbox in the table for the relevant line type. Table lines that use this line type are output on
one page.
Protection against page break for several table lines
- Expand the main area of your table node in the navigation tree.
- Insert a file node for the table lines to be protected in the main area.
- If you have already created table lines in the main area, you can put the lines that you want to protect again page break under the file
using Drag&Drop. Otherwise, create the table lines as subnodes of the file.
- Choose the Output Options tab page of the file node and set the Page Protection option. All table lines that are in the file with the Page
Protection option set are output on one page.
In 4.6, Alternatively in a paragraph format use the Page protection attribute to determine whether or not to display a paragraph completely
on one page. Mark it if you want to avoid that a paragraph is split up by a page break. If on the current page (only in the main window)
there is not enough space left for the paragraph, the entire paragraph appears on the next page.
Details information about SAP Barcodes
A barcode solution consists of the following:
- a barcode printer
- a barcode reader
- a mobile data collection application/program
A barcode label is a special symbology to represent human readable information such as a material number or batch number
in machine readable format.
There are different symbologies for different applications and different industries. Luckily, you need not worry to much about that as the
logistics supply chain has mostly standardized on 3 of 9 and 128 barcode symbologies - which all barcode readers support and which SAP
support natively in it's printing protocols.
You can print barcodes from SAP by modifying an existing output form.
Behind every output form is a print program that collects all the data and then pass it to the form. The form contains the layout as well as
the font, line and paragraph formats. These forms are designed using SAPScript (a very easy but frustratingly simplistic form format
language) or SmartForms that is more of a graphical form design tool.
Barcodes are nothing more than a font definition and is part of the style sheet associated with a particular SAPScript form. The most
important aspect is to place a parameter in the line of the form that points to the data element that you want to represent as barcode on
the form, i.e. material number. Next you need to set the font for that parameter value to one of the supported barcode symbologies.
The next part of the equation can be a bit tricky as you will need to get a printer to print that barcode font. Regular laser printers does not
normally print barcode fonts, only specialized industrial printers that is specifically designed to support that protocol and that uses
specialized label media and heat transfer (resin) ribbon to create the sharp image required for barcodes.
Not to fear though, there are two ways to get around this:
- You can have your IT department do some research -
most laser printers can accept a font cartridge/dimm chip (similar to computer memory), called a BarDIMM that will allow a laser printer to
support the printing of barcodes.
- Secondly, you can buy software that you can upload in your SAP pri
regards..
seshu.
Maybe you are looking for
-
Web Services Client is not working fine on JBOSS 4.0.4.GA
Dear Team, we had JBOSS AS 4.0.3 and web services was build on EJB which was working fine. we new have to migrate it to JBOSS 4.0.4.GA Application Server.... we have generated wsdl, webservices.xml and jaxrpc-mapping.xml file from wstools.exe of JBOS
-
Snow Leopard Upgrade Questions
Hello Folks, I am a newbie to MacBooks. I just "created" two MacBooks using "donor" parts (which I affectionately call "FrankenMacs" LOL). Both MacBooks are Model A1181, late 2007-vintage with the Intel 2.2GHz Core 2 Duo processor and running Leopa
-
My new Dell computer with windows 8, when I open my iTunes and plug my iPhone 5 in the computer does not see my phony, why?
-
Bought a Macbook Pro used with wiped HDD
Hello, I recently bought a used early 2011 Macbook pro. It had Snow Leopard installed but was wiped clean before the privious owner sold it to me. So I am wondering what I can do to reinstall an OS. Obviously I want the most up to date but it seems t
-
Setting "work Time" on a outbound call?
I have a request for me to set "work Time" built in after a outbound call. So if the user makes a call from the agent and then after they hang up it would wait 30 seconds before presenting them a call. I have UCCX 7.2 Express Enhan