Hi Alex,
The functionality does not exist at the moment.
Please go ahead and vote for this Idea :
Only workarounds available at this point:
1) Manually increasing the size of the field
2) Building a Manual Crosstab. A Manual crosstab, however cannot have dynamic columns, so you need to know how many columns your crosstab will have in advance.
-Abhilash
hi pradeep,
as u said i have reinstalled after restarting the system
still the same problem is repeating,
hi ranjay,
tried as u said, not successful.
Hi Sameer,
SCN already have certain documents similar to your request. Refer below link to develop your skills.
Debugging for Functional Consultants
http://www.itpsap.com/blog/2014/02/18/debugging-abap-for-functional-teams-part-1/
Regards
Terence
Hi Experts,
Greetings...!!!!
I am facing a problem with communication method in message output type. I am sending PO via external mail and I am maintained “Print Only” as a setting for storage mode in message output type and in MN05 for specific condition.
But when I create PO and go to message tab and check communication then for message output I found “Print and Archive” comes by default.
I feel I am missing some settings. Where I made settings in MN05 and for specific message Output type only at these two places. If I am maintain a Print Only as storage mode then in PO Messages tab communication setting should come as maintained that is Print only for Storage Mode.
Please help me to solve the issue. Suggest which OSS need to impliment.
Thanks
Hi Geriec,
There are couple of ways to do it.
But before that, do you intend to group the items in FPY1 with your set parameters or you want to clear only those items which fall under the set parameter?
I mean, do you only want to clear off those items which have specific type (with document type and/or main/sub) of open FICA document that are due in current month? Or you want to clear off all of them but want to group them (separate clearing document) with set type of open fica documents and month of due date ?
Thanks,
Bodhisattwa
Vendor can be defaulted by using source of supply.
There are 3 types of source of supplies can be used in standard SAP system.
1. Source list.
2. Info record.
3. Contract.
Else, you need to enhance yourself. Read this wiki for more details Source Determination within ECC system in Purchasing - ERP SCM - SCN Wiki
screen shots please.
NP 
Hello Alok,
Thanks a lot for your reply.
The issue has been resolved. There was no problem with aggregation level.
When I copy (MC8J) the same old jobs into new jobs (with same selection, activity, version) and assigned the new jobs in process chain by replacing with old one, it ran sucessfully.
If you run job with MC8g, both new and old jobs showing same spools in sm37.
It is very hard to understand that because of job number it was failing in the process chain with above errors. Trying to understand technical background.
For example- Old job number- R_CR_M_1NA
New Job Number- R_M_CROS_1
Regards,
Sachin
Hi,
In tcode RESRSE, is there an available authorization object to limit authorization (that is the settlement process) per Business Entity?
In a set up where there are multiple Business Entities under one company code, a user is allowed to do settlement for other business entity/s though only authorized for a specific BE.
Currently in our business process, for one company code multiple business entities are defined. Though under one company code, there are different users assigned for each BE. With this, authorization must be limited to BE level.
Is this a system standard behaviour? For RESRSE, authorization is up to company code level only?
Thanks.
Dear all.
We need multiple credit analysis t at the same time they need to release the sales order in FSCM we have created sales order and it is giving the error message that credit limit has been exceed now the order has been blocked we want to trigger the workflow for multiple credit analysis ts i have maintained two BP in BP master record(credit management) these two are created as employees with either of the persons id Dispute case is creating at a time not for both ids is there any group concept for credit analysists if one person is not available another person can release the credit block
mail is generating for both BP(Credit analysis ts) but this case id is with one credit anyalysist id
we need more than one credit analysis t when the Dispute case has been created after exceeding the credit limit of SD sales order. Dispute case need to be created with analysis t group or all credit analysis ts now it is showing with one person id
thanks®ards,
Madhav.
Hi Nithin,
Can you please set the number of IDOC segment per XI message then test this again?
It is the package size.
regards,
Harish
Dear SAP Gurus,
When posting in the T-code: FB50 we are getting an error message saying GL account Requires Tax code.
Initially our client is not facing this issue, only after the version upgrade they are facing this issue.
Checked the FS00 for that specific GL account in control data- TAX category < input tax account is given posting without tax allowed is given.
Any help on this is really appreciated.
Regards,
Deepak Pagare
Hi Hùng,
Check that user have write access to that data region, also check work status.
For performance issues you need to debug and ask ABAPer to enhance the performance of the code.
Andy
Hi Ramesh,
Do cross check in reports CJI3 and CJI1, whether you are getting the values. Also check in tables RPSCO and COSS/COSP for the values.
In case if you still feel the difference, try to reconstruct the project CJEN and check
Regards
Terence
Hello Atul,
my understanding reading the SAP Help LO-VC documentation is that a dummy material must be created and be part of the BOM components.
The characteristic QUANTITY shall be assigned to the dummy material.
The procedure using $COUNT_PARTS shall be allocated to the BOM item.
Here the extract for the doc:
Hope this could be of any help.
Thanks and regards,
Flavio
please rectify code ,,,,not able to fetch value in ekotx field in inner join
TABLES : LFA1 , EKKO ,EKBE .
TYPES : BEGIN OF TY_LFA1 ,
LIFNR TYPE LFA1-LIFNR ,
LAND1 TYPE LFA1-LAND1 ,
NAME1 TYPE LFA1-NAME1 ,
ORT01 TYPE LFA1-ORT01 ,
END OF TY_LFA1.
TYPES : BEGIN OF TY_EKKO_T024E,
EBELN TYPE EKKO-EBELN ,
BUKRS TYPE EKKO-BUKRS ,
* EKORG TYPE EKKO-EKORG ,
EKGRP TYPE EKKO-EKGRP ,
BEDAT TYPE EKKO-BEDAT ,
EKORG TYPE T024E-EKORG ,
EKOTX TYPE T024E-EKOTX ,
END OF TY_EKKO_T024E .
TYPES : BEGIN OF TY_T001 ,
BUTXT TYPE T001-BUTXT ,
BUKRS TYPE T001-BUKRS ,
END OF TY_T001 .
TYPES : BEGIN OF TY_T024 ,
EKGRP TYPE T024-EKGRP ,
EKNAM TYPE T024-EKNAM ,
END OF TY_T024 .
TYPES : BEGIN OF TY_FINALDETAIL ,
EBELN TYPE EKKO-EBELN ,
BUKRS TYPE EKKO-BUKRS ,
EKORG TYPE EKKO-EKORG ,
EKGRP TYPE EKKO-EKGRP ,
BEDAT TYPE EKKO-BEDAT ,
EKOTX TYPE T024E-EKOTX ,
BUTXT TYPE T001-BUTXT ,
EKNAM TYPE T024-EKNAM ,
END OF TY_FINALDETAIL .
TYPES : BEGIN OF TY_EKBE ,
EBELN TYPE EKBE-EBELN ,
EBELP TYPE EKBE-EBELP ,
VGABE TYPE EKBE-VGABE ,
BELNR TYPE EKBE-BELNR ,
BUZEI TYPE EKBE-BUZEI ,
BUDAT TYPE EKBE-BUDAT ,
END OF TY_EKBE .
************************************************************************
* INTERNAL TABLE *
************************************************************************
DATA : T_LFA1 TYPE STANDARD TABLE OF TY_LFA1 INITIAL SIZE 1 ,
T_EKKO_T024E TYPE STANDARD TABLE OF TY_EKKO_T024E INITIAL SIZE 1 ,
T_T001 TYPE STANDARD TABLE OF TY_T001 INITIAL SIZE 1 ,
T_T024 TYPE STANDARD TABLE OF TY_T024 INITIAL SIZE 1 ,
T_FINALDETAIL TYPE STANDARD TABLE OF TY_FINALDETAIL INITIAL SIZE 1 ,
T_EKBE TYPE STANDARD TABLE OF TY_EKBE INITIAL SIZE 1 .
************************************************************************
* WORK AREA *
************************************************************************
DATA : W_LFA1 TYPE TY_LFA1 ,
W_EKKO_T024E TYPE TY_EKKO_T024E ,
W_T001 TYPE TY_T001 ,
W_T024 TYPE TY_T024 ,
W_FINALDETAIL TYPE TY_FINALDETAIL ,
W_EKBE TYPE TY_EKBE ,
X TYPE I ,
FNAME(20).
************************************************************************
* SELECTION SCREEN *
************************************************************************
SELECT-OPTIONS : S_LIFNR FOR LFA1-LIFNR ,
S_EKORG FOR EKKO-EKORG ,
S_EKGRP FOR EKKO-EKGRP ,
S_BUKRS FOR EKKO-BUKRS .
************************************************************************
* BASIC LIST *
************************************************************************
SELECT LIFNR
LAND1
NAME1
ORT01
FROM LFA1 INTO TABLE T_LFA1
WHERE LIFNR IN S_LIFNR .
LOOP AT T_LFA1 INTO W_LFA1 .
WRITE : /05 W_LFA1-LIFNR , " VENDOR NO
40 W_LFA1-LAND1 , "COUNTRY
80 W_LFA1-NAME1 , " VENDOR NAME
120 W_LFA1-ORT01 . " CITY
HIDE : W_LFA1-LIFNR .
AT LAST .
X = SY-LINCT - SY-LINNO .
RESERVE X LINES .
ENDAT .
ENDLOOP .
************************************************************************
* *
************************************************************************
AT LINE-SELECTION .
GET CURSOR FIELD FNAME .
CASE SY-LSIND .
WHEN '1'.
************************************************************************
* FIRST DETAIL LIST *
************************************************************************
IF FNAME = 'W_LFA1-LIFNR'.
SELECT E~EBELN
E~BUKRS
E~EKORG
E~EKGRP
E~BEDAT
T~EKOTX
INTO TABLE T_EKKO_T024E
FROM EKKO AS E
INNER JOIN
T024E AS T
ON E~EKORG = T~EKORG
WHERE LIFNR = W_LFA1-LIFNR
AND E~EKGRP IN S_EKGRP
AND E~EKORG IN S_EKORG
AND E~BUKRS IN S_BUKRS .
*
WRITE 'TEST' .
SELECT
BUTXT
BUKRS FROM T001 INTO TABLE T_T001
FOR ALL ENTRIES IN T_EKKO_T024E
WHERE BUKRS = T_EKKO_T024E-BUKRS .
*WRITE 'TEST' .
*SELECT EKOTX
* EKORG FROM T024E INTO TABLE T_EKKO_T024E .
*
* WRITE 'TEST'.
SELECT EKGRP
EKNAM FROM T024 INTO TABLE T_T024
FOR ALL ENTRIES IN T_EKKO_T024E
WHERE EKGRP = T_EKKO_T024E-EKGRP .
*WRITE 'TEST'.
LOOP AT T_EKKO_T024E INTO W_EKKO_T024E .
MOVE-CORRESPONDING W_EKKO_T024E TO W_FINALDETAIL .
**
READ TABLE T_T001 INTO W_T001 WITH KEY BUKRS = W_EKKO_T024E-BUKRS .
W_FINALDETAIL-BUTXT = W_T001-BUTXT .
*
READ TABLE T_T024 INTO W_T024 WITH KEY EKGRP = W_EKKO_T024E-EKGRP .
W_FINALDETAIL-EKNAM = W_T024-EKNAM .
*
APPEND W_FINALDETAIL TO T_FINALDETAIL.
ENDLOOP .
IF SY-SUBRC = 0 .
**
LOOP AT T_FINALDETAIL INTO W_FINALDETAIL.
WRITE : /05 W_FINALDETAIL-EBELN ,
40 W_FINALDETAIL-BUKRS,
80 W_FINALDETAIL-EKORG ,
120 W_FINALDETAIL-EKGRP ,
160 W_FINALDETAIL-BEDAT,
240 W_FINALDETAIL-EKOTX ,
280 W_FINALDETAIL-BUTXT,
320 W_FINALDETAIL-EKNAM .
HIDE : W_FINALDETAIL-EBELN .
AT LAST .
X = SY-LINCT - SY-LINNO .
RESERVE X LINES .
ENDAT .
ENDLOOP .
ELSE .
MESSAGE S018(YMSG) WITH W_LFA1-LIFNR .
ENDIF .
ELSE .
MESSAGE S016(YMSG) .
ENDIF .
WHEN '2' .
************************************************************************
* SECOND DETAIL LIST *
************************************************************************
SELECT EBELN
EBELP
VGABE
BELNR
BUZEI
BUDAT FROM EKBE INTO TABLE T_EKBE .
*WRITE 'TEST'.
LOOP AT T_EKBE INTO W_EKBE .
WRITE : /05 W_EKBE-EBELN ,
40 W_EKBE-EBELP ,
80 W_EKBE-VGABE ,
120 W_EKBE-BELNR ,
160 W_EKBE-BUZEI ,
200 W_EKBE-BUDAT .
AT LAST .
X = SY-LINCT - SY-LINNO .
RESERVE X LINES .
ENDAT .
ENDLOOP .
ENDCASE .
************************************************************************
* TOP OF PAGE FOR BASIC LIST *
************************************************************************
TOP-OF-PAGE .
WRITE :/80'VENDOR MASTER DATA '.
ULINE .
WRITE : /05 'VENDOR NUMBER',
40 'VENDOR NAME ',
80 'CITY',
120 'COUNTRY'.
ULINE .
************************************************************************
* END OF PAGE FOR BOTH BASIC AND DETAIL LIST *
************************************************************************
END-OF-PAGE .
ULINE .
WRITE :/80 'PAGE ENDS',SY-PAGNO .
ULINE .
************************************************************************
* TOP OF PAGE FOR DETAIL LIST *
************************************************************************
TOP-OF-PAGE DURING LINE-SELECTION .
CASE SY-LSIND .
WHEN '1'.
WRITE : /80'PURCHASE ORDER DATA'.
ULINE .
WRITE :/05'VENDOR NO:', W_LFA1-LIFNR ,40 SY-VLINE , 80 'VENDOR NAME:',W_LFA1-NAME1 .
ULINE .
WRITE :/05'PO NUMBER',
40'P DOC DATE',
80'COMP CODE',
120'COMP CODE NAME',
160'P ORG',
200'P ORG NAME',
240'P GRP',
280'P GRP NAME'.
ULINE .
WHEN '2' .
WRITE:/80'PURCHASE ORDER HISTORY'.
ULINE .
WRITE :/05'VENDOR NO:',W_LFA1-LIFNR , 40 SY-VLINE , 80'VENDOR NAME :',W_LFA1-NAME1 .
ULINE .
WRITE :/05'PO NUMBER:',W_FINALDETAIL-EBELN ,40 SY-VLINE , 80'P DOC DATE:',W_FINALDETAIL-BEDAT .
ULINE .
WRITE :/05'P DOC NOC',
40 'ITEM NO OF P DOC ',
80 'EVENT TYPE',
120 'NO OF MAT DOC ',
160 'ITEM IN MAT DOC ',
200 'POSTING DATE IN DOC'.
ULINE .
ENDCASE .
Go to table BSEG and enter clearing document (Hope additionally you have company code and year) and in output you can find the document numbers cleared through the clearing document.
Best Regards,
Chirag Panchal
Hi Kurt,
The only 'horizontal' alignment options available in CR is under the 'Paragraph' tab (Right-click the field > Format Field > Paragraph tab).
When the text is rotated the horizontal alignment works from the left most margin of the field. You may manually insert new line feeds inside the text box to center align on the horizontal axis.
-Abhilash
