Leading zeros in the Product allocation characteristic combinations.

Hi All,
I am copying Characteristic combination from planning area to product allocation group, after i complete the transaction system is automatically preceding the zeroes to the product number.
I have one the following activities before copying CVC of planning area to product allocation group.
against all the Product allocation settings.
2.Created the MPOS with product (characteristic length of Product is 18), Customer and Allocation object.
3.Created planning area and planning book.
4.Copied cvc combination from planning are to product allocation group and also copied planning area values in to Product allocation group.
5.Tried to check in the ATP simulation mode, while I was doing system has given no characteristic combination found, when I checked Product is preceding zeros as per the filed MATNR length 40 and this MATNR is selected from the Product allocation field catalog, But when I add zeros to product system is performing Product allocations in simulation mode.
6.Tried triggering gATP Product allocations by creating Order in ECC, here also it has given same error No characteristic combination exists.
When I did initial R&D on this. I found that material number in the product allocation characteristic combination is leading by zeros for ex:- 000000000000000002200325.
Could any one please suggest me what to do on this.
Thanks and Regards,
T.Muthyalappa

Hi Muthyalappa ,
If i have understood your question properly , then my guess is you should be facing this problem only for numeric material codes. Try out the following things
1. Execute the same test condition for a non numeric material. I believe it will work perfectly .
2. For numeric material codes it is not working because of the difference in MATNR length between ECC and APO. In ECC the maximum possible MATNR length is 18 char whereas it is 40 chars in APO. So as per std SAP functionality the numeric materials get concatenated with leading zeros when you try to transfer it (or carry out any kind of processing ) from ECC to APO.
ex consider material 12345. In ECC it will be stored internally as 13 leading zero's followed by12345 . But in APO it will be stored as 35 leading zero's followed by 12345. Your issue is the system does not recognize the CVC that has this material as characteristic. At the time of cvc creation / change make sure your material characteristic ( especially for numeric material codes) totally has 40 chars . Pack it with leading zeros and make the material length 40.
Try this out and update me .
Thanks
Saradha

Similar Messages

Complications in the Product Allocation

Dear SAP Gurus,
I am facing lot of problems in configuring the Product Allocation.
Problem-01
I started creating new Info Structure S561 copying the existing Info Structure S140 as the Info Structure is to be assigned in OV3Z (Specify hierarchy).
The problem is that the Table MCVOBJECT is not appearing in the u201CCharacteristics for 0001 Incoming Orders Quantityu201D in the transaction code MC25. I tried to insert the Table name as MCVOBJECT and Field name as KONOB against the characteristics u201CProd Allocation obj.u201D but I got the error message as u201COnly source fields from MC Communication structures allowedu201D
Only few Table names are available after pressing F4.
Please help me how I can put the Table name MCVOBJECT and field name KONOB in the Characteristics for MC25.
Problem-02
In OVZ0 (Define Flow according to requirement category) I am not able to create new Requirement even in the change Mode. But I found some of them started with Z i.e. it has been created by somebody. I am in IDES system.
Problem-03
The same issue in OVZ8 (Process flow for each Schedule line Category) I am not able to create new Requirement even in the change Mode. But I found some of them started with Z i.e. it has been created by somebody.
Please guide me how to create a new requirement and assign it.
Problem-04
When I am checking in OV8Z (Check setting in Product Allocationu201D, the following comments appear. If anybody guide me on this basis I will be grateful to him.
u201CProd.alloc.detmtn prod: PRODUCT Description: Various Items
Use for following materials:
    1478
Method:
    Cumulative check
      Step: 01 Description: First step Info struct.: S561
        Info struct.
          Planning version 000 is defined for info structure S561 .
          Periodicity M ( ) is set for info structure S561 .
        Update
          Updating is not defined for S561 at schedule line level!
          The update date is not permitted for S561 (permitted; MBDAT , WADAT , EDATU )!
          The period settings for info structure S561 agree
          The info structure is updated synchronously.
          Formula 146 is used for the order incoming quantity
          Not every characteristic has a formula
        Plng
          No allocation quantities have been defined for product allocation object MCA1 !
          End of allocation validity is always end of a period (PRODUCT ,01 ).
          The product allocation objects are entered in the planning hierarchy.u201D
Problem-05
Where should I put the quantity because when I am creating Sales Order no Product Allocation function is working.
Problem-06
I have used Transaction code MC8A for creating Planning type but every time I put some value and save but after that in change mode I am not finding those values.
Regards,
Jans

Hi Lakshmpathi,
Please help me in solving these problems,
Thanks,
Jans

Want to hide/eliminate the leading Zeros in the Variable popup for0MATERIAL

I have a requirement where 0MATERIAL is having leading zeros and it has the MATN1 conversion routine in the production system.I want to only remove the leading zeros in the Variable popup in report for 0 MATERIAL witohut changing the definition of the object as it has too much production data to change.
Best Regards
Tagore

Hi,
You will have to write some code in F4 help BADI, please refer the sap note 1416952. And you can take help of following function module to remove leading zeros,
CONVERSION_EXIT_ALPHA_OUTPUT.
If above thing doesn't help then you will have to create virtual key figure.
Regards,
Durgesh.

Need leading Zeros in the excel sheet which is sent from ABAP

Hi ,
I am downloading data from SAP to excel sheet using the WS_DOWNLOAD Function Module. The numeric data in not having leading zeros. if it is 0010 it is displaying 10 in the excel sheet . i need the leading zeros in the excel sheet. without manulally changing it to Text in the excel sheet .
   Is there any way to do it .
Thanks,
Chetan

Hi Chetan,
CALL FUNCTION 'WS_DOWNLOAD'
    EXPORTING
      filename                = w_file_path
      filetype                = 'DBF'                       "declare the File type as DBF then leading zeros will appear
      write_field_separator   = 'X'
      confirm_overwrite       = 'X'
    TABLES
      data_tab                = Itab.
Regards,
Prabhudas

Suppressing Leading Zeroes in the Query output

Hi,
I have selected a data field(0MATERIAL) as a free characteristics, It displays text and key and the key has leading zeroes.
In the infoobject 0MATERIAL, ALPHA conversion routine is not selected, I can't change and insert the ALPHA right now because it would end up with reloading a large volume of data in different targets. To avoid this or to reduce the impact, in the reverse way,
Could it be possible to suppress this leading zeroes at the query level? I was hoping that there would be a change that I could make at the query level, since it is 0Material and am looking at the point of minimal impact.
Thank You.

Hi Senthil,
create InfoObject ZMATERIAL like a copy of 0MATERIAL, delete all the attributes and insert ALPHA conversion.
Insert this ZMATERIAL like display attribute of 0MATERIAL. In InfoSource for 0MATERIAL map also ZMATERIAL with the same field that is feeding 0MATERIAL (MATNL). In your query insert 0MATERIAL and ZMATERIAL, and then hide 0MATERIAL (you need to insert also 0MATERIAL because ZMATERIAL is only in display), you will see only the values of ZMATERIAL, that is the material without the zeros in front.
You can also decide to transform ZMATERIAL like navigational attribute, but in this case you have to change all the structure where do you want ZMATERIAL, because you need to flag it like navigational in that specific structure.
Ciao.
Riccardo.

No leading zeros in the assignment field on a billing doc header

Can someone tell me how I can get the assigment field in a billing doc not to show any leading zero's so when the assigment field is populated in the accounting doc it will not show the zeros either .
At the moment I have the sales order PO set in copy control to show in the reference field and the assigment field of the billing doc header but need it to show no leading zeros in the accounting doc even if there is some in the SO.
I.E
sales orde PO no              Assignment field in billing doc             accounting doc
0000012345                      0000012345                                        0000012345
i need it to show NO zeros
                                           12345                                                  12345
any ideas

check this thread
VBRK-XBLNR not copied to BKPF-XBLNR in transaction VF11.
Note: Pls Text Removed
Edited by: Lakshmipathi on Nov 1, 2011 10:42 AM
Please dont ask for points in each of your suggestion and deviate the forum rules

Display leading zeros in the ALV

Hello All,
My requirement is to display leading zeros in the ALV. The leading zeros are not getting displayed. Please suggest how do I achieve this. I have tries NO_ZERO = ' ' and lzero = ' '.
Thanks in advance.
Regards,
Anju

Here is the Sample code for your ref
type-pools: slis.
data: begin of t_itab occurs 0,
       col1 type matnr,
       col2 type char10,
      end of t_itab.
data: t_fieldcat type slis_t_fieldcat_alv,
      w_fieldcat type slis_fieldcat_alv.
t_itab-col1 = 10.
t_itab-col2 = 'A'.
append t_itab.
clear t_itab.
t_itab-col1 = 11.
t_itab-col2 = 'B'.
append t_itab.
clear t_itab.
loop at t_itab.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input         = t_itab-col1
   IMPORTING
     OUTPUT        = t_itab-col1 .
   modify t_itab index sy-tabix.
endloop.
w_fieldcat-fieldname = 'COL1'.
w_fieldcat-lzero = 'X'.
append w_fieldcat to t_fieldcat.
clear w_fieldcat.
w_fieldcat-fieldname = 'COL2'.
append w_fieldcat to t_fieldcat.
clear w_fieldcat.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   I_CALLBACK_PROGRAM                = sy-repid
   IT_FIELDCAT                       = t_fieldcat
   I_SAVE                            = 'X'
TABLES
    t_outtab                          = t_itab
EXCEPTIONS
   PROGRAM_ERROR                     = 1
   OTHERS                            = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards,
Bhavana

How to remove leading zeros from the screen?

Hello friends,
I am working on dialog programming.
I have a field with is NUMC 13. so when value is populated, It removes the leading zeros.
How can I display the my value with leading zeros on the screen painter?

Call SE51, layout, double-click on field, attributes, tab Program, check Leading zeros.
Regards,
Raymond

Need to show leading zeros in the number field when printed from RDF

We have a requirement to show leading zeros in the rdf output.
We cannot use a format mask to achieve the same as the length of the field is not fixed.
for ex if we have 0.68 then the same is printed in RDF as .68
we cannot use a format mask as the length of the field is not fixed.
we need to
Kindly suggest if any solution exists for the same.

the numbers after the decima can be anything..
it can range between 2 to 10 or more...
as told by you if we put the format as to_char(.68,'90.99') it shall give 0.68 but what for numbers like0.678,0.4567,0.765433 it will display only 2 digits after the decimal...
The requirement is to dispaly the number as it is ,only the zeroes before the decimal should stay intact..
we are not able to achieve this in rdf output..
if it is
0.678 then 0.678 shld be dispalyed
0.4567 then 0.4567
0.765433 then 0.765433
one format mask shld wrk for all the above..
we would not be changing the format mask for each number....

BAPI to remove leading zeros from the serial number

Hi All ,
plz can anybody suggest me the alternative BAPI for 'BAPI_SERVNOT_MODIFY_DATA ',whose function is to delete the leading zeros,from the serial number.
Thanks.

Perhaps instead of using a BAPI you can code it like this.
DATA:serial(10) TYPE n VALUE '0000340078',
pos TYPE i VALUE 1.
START-OF-SELECTION.
WHILE pos <= 10 AND serial+pos(1) = 0.
pos = pos + 1.
ENDWHILE.
REPLACE ALL OCCURRENCES OF '0' IN serial(pos) WITH space.
WRITE serial.

Leading zero for the instance

hi,
my numbers looks like 0 or -0,23 or ,45...
but i want to have a leading zero, e.g. 0,0 or 0,45
i know that i can use to_char(xxx,'format') in queries,
but i want to have the leading zero for the whole instance.
is that possible?
thx.

In cas you use SQL*Plus for your queries modify your login file
SET NUMFORMAT ...http://download-west.oracle.com/docs/cd/B10501_01/server.920/a90842/ch3.htm#1005686

Check the Product Allocation Settings - /SAPAPO/ATPCQ_CHECK

Hello,
I have an issue when I use the Check the Product Allocation Settings (TCODE: /SAPAPO/ATPCQ_CHECK), the system returns ''SYST: Period 000 is not valid in financial year variant J1''. J1 is my calendar and I using this calendar for all another Product Allocation Groups whitout erros. I just have this information by system report.
I sincerely don't no why some groups have this issue because all groups are using the same setup.
Anybody have any ideia?
Thanks,
-Ralph

Hi Santosh,
First thank you for help me, following your instructions I have made a investigation and now I know thatu2019s
another team doing a test with this calendar in R/3, for FI, and really have differences between systems. Your direction are correctly.
Thank you very much!
Ralph Veiga

How is the product allocation work?

How is the product allocation works? (material master: Basic Data 1,) where is the place to maintain the parameters?
point will given

Product Allocation
Configuration Overview; Allocation Specific Usage
1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation.
2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material
3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed
4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check.
5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials
6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant.
7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant
8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified.
9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy
10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors
11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered
12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).
Regards
Jitesh

Truncating leading zeros for the data

hi ,
I am doing a conversion project from oracle source system(DB2) to BI system. I have a situation here:
I am extracting material numbers from source system(DB2) into a ZXXXX characteristic and in the transfer structure i checked the conversion as well and for infoobject ZXXXX, i am using ALPHA conversion. but the data i get is truncating material numbers. For example, 050302 is coming as 50302 and truncating leading zero. I am not sure what needs to be done here.
Please advise..
Thanks in advance...

Hi J Dorson,
This is the expected bahaviour if your InfoObject is configured to have ALPHA conversion. If the zero's in front of the material number is needed, then turn-off ALPHA conversion in your InfoObject (e.g. by removing the conversion exit).

Remove the leading Zero from the Query output in SAP BW ?

Hi
Experts,
Vendor Number loaded as (0000010076) from R/3 to SAP BW.
How to remove Prefix of Zero for the Vendor Number(0000010076) from Quey outpt.
Regards.
ASIT

Hi,
Please check out this thread.
Remove leading zeros
Also check if there is any conversion routine used for that particular infoobject.
If ALPHA conversion is selected for your infoobject then it will automatically take away the leading zeros at query level.
Regards,
AL
Edited by: AL1112 on Sep 16, 2011 9:15 AM

Leading zeros in the Product allocation characteristic combinations.

Similar Messages

Maybe you are looking for