SAP standard PO smartforms in ECC 6

The SAP Best Practices Preconfigured Smart Forms are for ERP 2004 (ECC 5.0) are no longer available in ECC 6. SAP has delivered the preconfigured SmartForms as separate SAP Best Practices solution for other releases.

The preconfigured SmartForms are delivered with the country-specific SAP Best Practices Baseline and Industry packages. Please check http://service.sap.com/bestpractices for availability.

For more details please refer the following notes:

Note 843193 – SAP Best Practices for Preconfigured SmartForms

Note 852250 – updated /SMB40/ preconfigured form for 470 and 640

Also please check: https://help.sap.com/bp_af603/BBLibrary/General/SAP_Smart_Forms_Overview.htm

See also the Development Master List in the link: https://help.sap.com/bp_af603/BBLibrary/html/153_EN_CN.htm

Downloading pre-configured Smart Forms:

Procedure to download the pre-configured Smart Forms is explained in the following document which may require you to log into service market place.

https://websmp208.sap-ag.de/~sapidb/011000358700000510932012E.pdf

When I personally contacted SAP through an OSS message for one of my client in ECC 6, I got the following response:

Thank you for contacting SAP Global Support Center.

Now, the preconfigured SmartForms are delivered with the country-specific SAP Best Practices Baseline and Industry packages, therefore if you want to use new smartform /SMBA0/* in ECC 600 system, you must implement SAP Best Practices Package. Please check http://service.sap.com/bestpractices for availability.

Please review the information provided in Note Number 843193.

843193 SAP Best Practices for Preconfigured SmartForms

If you are upgrading from R/3 470 or ECC 500 to ECC 600, the smartform /SMB40/* will be lost in ECC 600 system. if you still want to use smartforms /smb40/* in the ECC 600 system, you can download the smartforms and print programs from your old system , then upload them them to your new system and activate them.

For more information please also check the notes below as well:

833009 Release strategy for BP-BLERP(ECC 500)
852250 updated /SMB40/ preconfigured form for 470 and 640

I hope this answers your query.

For bestpractices in UK for ECC6 EHP6, please refer to SAP Note 1715617 – SAP Best Practices Baseline Package UK

For how to apply help please refer to OSS Note 1225909 – How to apply SAP Best Practices

 

FAQ Notes on Classification systems

  1. 943559 – FAQ: Frequently asked questions about the classifctn. system
  2. 1457136 – FAQ: Frequently asked questions about classifctn. system II
  3. 943560 – FAQ: Frequent problems in the classification system III
  4. 1588147 – FAQ: Frequent problems in the classification system IV
  5. 1424281 – FAQ: Classification for ECC and APO
  6. 1423729 – FAQ: Classification in APO

 

 

Characteristic Long Text change is not saved in SAP

Note that long texts for a characteristic can only be overwritten if at least one other change has been made, for example, a value change.  Thus, if you only change the long text for the characteristic from the class in the characteristic and you do not simultaneously change a value description for example, the system does not save the changes.

Refer OSS Note 408709 for more details on this.

CEBAN Fields / CEKKO fields available in standard SAP

Many times we are not infront of our system and want to know if a particular field is available to be considered as a characteristic in our release strategies. I found a couple of sites who just list the fields with out the descriptions and it becomes difficult to find out the descriptions if you do not have immediate access to a system. Hence all the field details of CEBAN and CEKKO communication structures are produced below for referencing when needed.

Component / Field Component / Field Type Data type Length Component / Field Descriptions
CEBAN – Communication Structure for Purchase Requisition
BSART BBSRT CHAR 4 Purchase Requisition Document Type
BSAKZ BSAKZ CHAR 1 Control indicator for purchasing document type
ESTKZ ESTKZ CHAR 1 Creation Indicator (Purchase Requisition/Schedule Lines)
EKGRP EKGRP CHAR 3 Purchasing Group
ERNAM ERNAM CHAR 12 Name of Person who Created the Object
ERDAT ERDAT DATS 8 Date on Which Record Was Created
AFNAM AFNAM CHAR 12 Name of Requisitioner/Requester
TXZ01 TXZ01 CHAR 40 Short Text
MATNR MATNR CHAR 18 Material Number
EMATN EMATNR CHAR 18 Material Number
WERKS EWERK CHAR 4 Plant
LGORT LGORT_D CHAR 4 Storage Location
BEDNR BEDNR CHAR 10 Requirement Tracking Number
MATKL MATKL CHAR 9 Material Group
RESWK RESWK CHAR 4 Supplying (Issuing) Plant in Stock Transport Order
MEINS BAMEI UNIT 3 Purchase Requisition Unit of Measure
BADAT BADAT DATS 8 Requisition (Request) Date
LPEIN LPEIN CHAR 1 Category of Delivery Date
LFDAT EINDT DATS 8 Item Delivery Date
FRGDT FRGDT DATS 8 Purchase Requisition Release Date
PSTYP PSTYP CHAR 1 Item Category in Purchasing Document
KNTTP KNTTP CHAR 1 Account Assignment Category
LIFNR WLIEF CHAR 10 Desired Vendor
FLIEF FLIEF CHAR 10 Fixed Vendor
EKORG EKORG CHAR 4 Purchasing Organization
VRTYP BSTYP CHAR 1 Purchasing Document Category
KONNR KONNR CHAR 10 Number of Principal Purchase Agreement
KTPNR KTPNR NUMC 5 Item Number of Principal Purchase Agreement
INFNR INFNR CHAR 10 Number of Purchasing Info Record
DISPO DISPO CHAR 3 MRP Controller (Materials Planner)
BWTAR BWTAR_D CHAR 10 Valuation Type
BMEIN BSTME UNIT 3 Purchase Order Unit of Measure
KANBA KBNKZ CHAR 1 Kanban Indicator
BPUEB BPUEB CHAR 1 Adopt Requisition Price in Purchase Order
USRC1 USRC1 CHAR 20 User field format character for release strategy
USRC2 USRC1 CHAR 20 User field format character for release strategy
USRN1 USRN1 NUMC 10 User field numeric for release strategy
USRN2 USRN1 NUMC 10 User field numeric for release strategy
GSWRT GSWRT CURR 13 Total Value of Item
.INCLUDE CEBANZZ   0 Communication Structure: Requisition Release for User Exit
PDUMMY DUMMY CHAR 1 Dummy function in length 1
.INCLUDE CACCOUNT   0 Release Strategy: Account Assignment Fields
SAKTO SAKNR CHAR 10 G/L Account Number
GSBER GSBER CHAR 4 Business Area
KOSTL KOSTL CHAR 10 Cost Center
VBELN VBELN CHAR 10 Sales and Distribution Document Number
VBELP POSNR_VA NUMC 6 Sales Document Item
VETEN ETENR NUMC 4 Delivery Schedule Line Number
ANLN1 ANLN1 CHAR 12 Main Asset Number
ANLN2 ANLN2 CHAR 4 Asset Subnumber
AUFNR AUFNR CHAR 12 Order Number
WEMPF WEMPF CHAR 12 Goods Recipient/Ship-To Party
ABLAD ABLAD CHAR 25 Unloading Point
KOKRS KOKRS CHAR 4 Controlling Area
KSTRG KSTRG CHAR 12 Cost Object
PAOBJNR RKEOBJNR NUMC 10 Profitability Segment Number (CO-PA)
PRCTR PRCTR CHAR 10 Profit Center
PS_PSP_PNR PS_PSP_PNR NUMC 8 Work Breakdown Structure Element (WBS Element)
NPLNR NPLNR CHAR 12 Network Number for Account Assignment
AUFPL CO_AUFPL NUMC 10 Routing number of operations in the order
IMKEY IMKEY CHAR 8 Internal Key for Real Estate Object
APLZL CIM_COUNT NUMC 8 Internal counter
VPTNR JV_PART CHAR 10 Partner account number
FIPOS FIPOS CHAR 14 Commitment Item
FISTL FISTL CHAR 16 Funds Center
GEBER BP_GEBER CHAR 10 Fund
DABRZ DABRBEZ DATS 8 Reference Date for Settlement
PSP_PNR PSP_PNR CHAR 24 Work breakdown structure element (WBS element)
GSFRG GSFRG CHAR 1 Overall release of purchase requisitions
GFWRT GFWRT CURR 15 Total value of requisition for overall release procedure
WAERS WAERS CUKY 5 Currency Key
REVNO REVNO CHAR 8 Version number in Purchasing
BLCKD BLCKD CHAR 1 Purchase Requisition Blocked
.APPEND /ISDFPS/DFP_CEBAN Append Structure 0 Append Structure for Defense for Release Strategy; CEBAN
PRIO_URG /ISDFPS/PRIO_URG NUMC 2 Requirement Urgency (Obsolete)
PRIO_REQ /ISDFPS/PRIO_REQ NUMC 3 Requirement Priority (Obsolete)
ADVCODE /ISDFPS/ADVCODE CHAR 2 Advice Code
STACODE /ISDFPS/STACODE CHAR 2 Status Code
         
CEEKKO – Communication Structure for External Purchasing documents
BUKRS BUKRS CHAR 4 Company Code
BSTYP BSTYP CHAR 1 Purchasing Document Category
BSART BSART CHAR 4 Order Type (Purchasing)
BSAKZ BSAKZ CHAR 1 Control indicator for purchasing document type
LIFNR ELIFN CHAR 10 Vendor Account Number
SPRAS SPRAS LANG 1 Language Key
EKORG EKORG CHAR 4 Purchasing Organization
EKGRP BKGRP CHAR 3 Purchasing Group
WAERS WAERS CUKY 5 Currency Key
BEDAT BEDAT DATS 8 Purchase Order Date
LLIEF LLIEF CHAR 10 Supplying Vendor
KUNNR KUNNR CHAR 10 Customer Number 1
RESWK RESWK CHAR 4 Supplying (Issuing) Plant in Stock Transport Order
LBLIF LBLIF CHAR 10 Field not used
INCO1 INCO1 CHAR 3 Incoterms (Part 1)
KTWRT KTWRT CURR 15 Cumulative Planned Value
LIFRE LIFRE CHAR 10 Different Invoicing Party
WERKS EWERK CHAR 4 Plant
MATKL MATKL CHAR 9 Material Group
LTSNR LTSNR CHAR 6 Vendor Subrange
USRC1 USRC1 CHAR 20 User field format character for release strategy
USRC2 USRC1 CHAR 20 User field format character for release strategy
USRN1 USRN1 NUMC 10 User field numeric for release strategy
USRN2 USRN1 NUMC 10 User field numeric for release strategy
GNETW GNETW CURR 15 Total net order value
SUBMI SUBMI CHAR 10 Collective Number
MEMORY MEMER CHAR 1 Purchase order not yet complete
KONNR KONNR CHAR 10 Number of Principal Purchase Agreement
REVNO REVNO CHAR 8 Version number in Purchasing
.INCLUDE CEKKOZZ Structure Type CEKKOZZ 0 Communication Structure: PO release for User Exit
PDUMMY DUMMY CHAR 1 Dummy function in length 1

ABEND. MMPV_DATE_CHECK: Errors occurred (see Note 1082841)

You come across this issue when you attempt to close the ezisting period and open the next period in MMPV if the new period is within 10 days (by default but is configurable) away from the current date in the system.

In the event that MMPV is mistakenly executed twice at the beginning of a period, the active period could be shifted to a future period.  As a consequence, all subsequent goods movement would be posted to the wrong period.

Note 1082841 provides a feature to prevent using MMPV to shift into a future period.  This feature is activated automatically after implementing this note and works with or without Material Ledger active. MMPV can continue only if the new period is within 10 days (by default but is configurable) away from the current date in the system. Otherwise, it will terminate and no change will be made and this error will be forced upon you.

To disable this feature, you must set parameter ID MMPV_READ_NOTE with the current date in the user parameters in form YYYYMMDD (Y = year, M = month, D = day).

To change the number of days to a value other than the default (10 days), set the following entry in table CKMLMVADMIN:

To disable this feature, you must set parameter ID MMPV_READ_NOTE with the current date in the user parameters in form YYYYMMDD (Y = year, M = month, D = day).

To change the number of days to a value other than the default (10 days), set the following entry in table CKMLMVADMIN:

KKEY  : MMPV_NUMBER_DAYS_ALLOWED
KDATA : <number of days MMPV is allowed>

To know more details on this please refer to the OSS Note 1082841

STMS – XT216 – 1 of 1 requests do not match the component version of the target system – XT 216

The versions of the software components in the source and target systems fortransport requests do not match. At the time of export, the release or the SP levelsoftware components () were different in the export system, when compared with the target system.

System Response

The import was not executed.

Procedure

If the software components in the target system have a lower Support Package Level, you need to implement the relevant Support Packages in the target system before importing the transport requests. If the release is different in the target system, you need to perform an upgrade before importing the transport requests.

If the software components in the target system have a higher Support Package Level or a higher release, it might not be possible to import the affected transport requests into this target system.

If it is not possible to bring the target system to the Support Package level or release of the source system, you need to decide in each individual case whether or not to import the requests. If you want to import the transport requests anyway, you can repeat the import with the option “Ignore Invalid Component Version”. However, depending on the content of the transport requests, this could lead to errors during the import.

Procedure to solve this issue

Branch to the Options tab in the Import Transport Request window and senect the check box “Ignore Invalid Component Version and select to continue and go ahead if you are confident to transport the request.

 

Cannot Edit VOFM – Object TFRM cannot be blocked: It will be displayed

You are trying to edit a formula in VOFM and system comes out with the Message VC295 – Object TFRM cannot be blocked: It will be displayed.

This happens when some one has opened VOFM for editing and then you are opening for editing. Since this is cross client activity, if an ABAP Consultant has opened it in one client, the system will come out with this message for you in other clients as well. So you can execute SM12 to see in clients if some one has locked the object TFRM and TFRMT.

Delayed update of the stock removal data in the outbound delivery during transfer order confirmation

You can delay update of the stock removal data in the outbound delivery during transfer order confirmation. This feature was added in ECC to reduce system locks during the update process and to improve general system performance. Up until SAP R/3 4.7, the system always updated this data immediately after confirmation of a transfer order item in the outbound delivery. In SAP R/3 Enterprise, you can now choose between different update times:

  • Update the outbound delivery after confirming a transfer order item (previous function)
  • Cumulated update of the outbound delivery after confirmation of the last item in the transfer order
  • Update the outbound delivery after confirming the last transfer order if there was an order split (several transfer orders per outbound delivery)