Releasing Supply Plans to DP using RTSCOPY

We have an issue where the batch job that releases supply plans from SNP to DP (time series to time series using /sapapo/rtscopy) cancels if anyone is logged in edit mode in DP planning book. Is there a way this can be circumvented ? We have set the planning area for all the locks and have tried all permuation combinations. However the job still cancels out if anyone is logged in DP.

You may try following,
Before executing the transaction, run one Zprogram which will check the user log into the DP planning book and stop their transaction send mail to them for information.
thats the reason these type of programs run after office hrs in background.

Similar Messages

RE: Using interfaces to alleviate supplier plan visibilityproble ms

Hallo Martin,
I am not sure I am answering directly to your question but...
You can apply an architectural pattern to break the supplier plan chain,
and using the name service to select the requested service dynamically
and selectively.
This pattern uses interfaces, and can be applied in several situation.
For your information I will present these ideas together with some tips
and tricks about the Name Service at Forum99.
Also the TN 11455 may help you.
Please feel free to contact me to have more information.
Best regards
Fabrizio Genesio
Datasign AG für Informatik
Ch. d'Eysins 53a
CH-1260 Nyon, Switzerland
Tel. : +41 22 361 04 04
Fax : +41 22 361 01 10
Mobile : +41 79 601 81 31
E-mail : mailto:[email protected]
Web : http://www.datasign.ch
-----Original Message-----
From: Martin G Nystrom [SMTP:[email protected]]
Sent: Thursday, 15 April 1999 11:13
To: [email protected]
Subject: Using interfaces to alleviate supplier plan
visibility problems
At FORUM97, someone from Born presented a paper on how to use
interfaces to
get around problems with supplier plan setups that restrict
visibility. Does
anyone have this presentation or can offer any pointers?
-martin
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Jeanne Hesler wrote:
>
The work-around was to include the c library as a supplier to the
project that will be using it. It's a little ugly, but it works. In
your case, you would need to include both libraries. It should not
cause platform problems, because even though it is a supplier, it will
not actually get loaded until you ask for it, and you will only ask for
the right one for the platform you are on. Just be sure that what you
include as a supplier is a library, and not a source project.Thank you so much! I tried this out last night and it works great! The
only downside is that at deployment time, Forte will require the C
library to be installed even on the platforms that don't support it, but
that's a small price to pay for the benefits we're getting. And maybe
someday Forte will fix the bug. :) Again, thanks for your help.
You should be able to use FindLibrary to load a dll, because that's what
you would be doing if you were using compiled libraries.I don't actually need to do this now, but I did figure out what I was
doing wrong when I tried this yesterday. Our DLL name was slightly
different from the name of the project directory, but I had it coded as
if it were the same. So of course Forte couldn't find the library to
load. Also, Forte apparently looks first for the compiled library and
then for the interpreted library, so when I was getting the error
message, the error message referred to the name of the interpreted
library and I assumed that's all it had looked for. Sure helps when you
spell things right!
Dale
=================================
Dale V. Georg
Senior Systems Analyst
Indus Consultancy Services
[email protected]
=================================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

TR: Supplier plans

Kevin,
you can analyse the entire Supplier Plan Hierarchy by using Leonardo.
This tool is provided by O.T. Consulting S.r.l., it access directly to
your Forté repository and provides a tree view with all the Supplier Plan
dependencies related to a specific project.
But to see all Leonardo features (partitioning,Import/Export, Builder,
Project Browser), Please have a look to our web site www.otconsulting.com and
download a Try and Buy Demo version.
You will have to send to us, [email protected], your party
information in order to receive the key code
Hope this help,
Massimiliano Delsante
O.T. Consulting S.r.l.
[email protected]
mobile : 0039 335 6678268
-----Message d'origine-----
De: Kevin Klein [SMTP:[email protected]]
Date: mercredi 27 janvier 1999 16:24
A: Forte Users
Objet: Supplier plans
Does any one know of a Forte or 3rd party utility to print out the
supplier
plan graph for an application? We are in the process of modularizing our
application using libraries and would find this information very useful.
I
already know how to use FSCRIPT to show the suppliers for an individual
plan, but I'm interested in seeing the supplier relationships for an
entire
application. Ideas, anyone?
Kevin Klein
Sycamore Group, LLC
Milwaukee, Wisconsin, USA
Mankind, when left to themselves, are unfit for their own government.
-- George Washington
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

check out Forte tech note 10448, order for importing projects.
There are a couple of postings for developer's apps as well in the archive.
-----Original Message-----
From: Kevin Klein [SMTP:[email protected]]
Sent: Wednesday, January 27, 1999 10:24 AM
To: Forte Users
Subject: Supplier plans
Does any one know of a Forte or 3rd party utility to print out the
supplier plan graph for an application? We are in the process of
modularizing our application using libraries and would find this
information very useful. I already know how to use FSCRIPT to show the
suppliers for an individual plan, but I'm interested in seeing the
supplier relationships for an entire application. Ideas, anyone?
Kevin Klein
Sycamore Group, LLC
Milwaukee, Wisconsin, USA
Mankind, when left to themselves, are unfit for their own government.
-- George Washington << File: Kevin Klein.vcf >> -
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Problem with Exception Worksheet using Data from Supply Plan Data Table

I added a series for a flag that indicates whether product is sourced from multiple manufacturing sites for a given customer and item. The flag is on the supply plan data table because it depends on the scenario. I created an exception worksheet for when the flag is set but all combinations are being displayed. If the flag is not set for a given combo then "Selected Page Item has No Data" is displayed in place of the table. I want only the combinations that meet the exception to be shown. I tried setting up an exception worksheet for customer shipments which is also on the supply plan data table but saw the same issue with all combinations being displayed whether or not the condition is met. Does anyone know of any issues with using exception worksheets with the supply plan data table? I searched the documentation and saw that exceptions behave differently with promotion series but this isn't a promotion.
I'm using Demantra version 7.2. Thanks for any help!
Edited by: user9253208 on Mar 30, 2010 6:40 AM

Thanks. We have come up with a workaround. While the combinations on the left are not affected by the exception, the data in the main table is so we moved as many levels as possible into the table. The performance is slow but the data is more useful, especially when exported into Excel. I was hoping for a better solution but I guess we'll just have to stick with what we've come up with.

Unable to make use of Service "Release Supplier Invoice"

We have recently installed EHP-3. I have been trying to make use of the following service
Under Repository Browser --> Package -- > OPS_SE_IVE_XI_PROXY
Enterprise Services -- > Server Proxies ---> II_IVE_E_INVOICEREPRELRQ (Double Click)
The Service Release Supplier Invoice with Service Interface name --> InvoiceERPReleaseRequest_In has status Active.
Everthing seems to in place... But I don't see the Service under SOA Manager.
Please advice, how to make use of the Service above....
Thanks in Advnace!!
Vikas

I have configured the Logical Port and able to publish other Services... but not able to find this Service itslelf under wspublish too..
This is the message comes under Dispaly Logs "No service(s) to be published with the given criteria.
Message no. MSG_CL_ER022"..
Thanks for your help
Vikas

Unable to use Service - Release Supplier Invoice

We have recently installed EHP-3. I have been trying to make use of the following service
Under Repository Browser --> Package -- > OPS_SE_IVE_XI_PROXY
Enterprise Services -- > Server Proxies ---> II_IVE_E_INVOICEREPRELRQ (Double Click)
The Service Release Supplier Invoice with Service Interface name --> InvoiceERPReleaseRequest_In has status Active.
Everthing seems to in place... But I don't see the Service under SOA Manager.
Please advice, how to make use of the Service above....
Thanks in Advnace!!
Vikas

Vikas,
To analyse your issue below, I would appreciate that you open an OSS ticket under component CA-SOA-WS with a detailed issue description (screenshots are very welcome).
Thanks,
Claudius

Using interfaces to alleviate supplier plan visibilityproblems

At FORUM97, someone from Born presented a paper on how to use interfaces to
get around problems with supplier plan setups that restrict visibility. Does
anyone have this presentation or can offer any pointers?
-martin
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Geoff Puterbaugh wrote:
>
I don't think you're missing anything here. I ran into the same
problem some months ago. If your dynamically-loaded class
has supplier plans, you have to go out and load them yourself.
I reported this bug to Forte and they said (I think)
that it would be fixed in R4. Not R3.Yeah, I was just playing around with it some more, and it seems that
you're right that from your dynamically-loaded class you can go out and
load the supplier plan classes dynamically as well. The problem with
this, of course, is that when you dynamically load a class, you get a
generic Object back; you can't really use it unless you cast it, and you
can't cast it because Forte "can't get scope for class!" And further,
in my case the classes I want to load are from a C-wrapper library,
which doesn't even have BTD/BTX files, so you can't use findLibrary() to
load it anyway. Argh! I finally find a compelling reason to use
interfaces, and it won't work!!
Thanks for your help, though. :)
Dale
=================================
Dale V. Georg
Senior Systems Analyst
Indus Consultancy Services
[email protected]
=================================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Release Demand Planning to Supply Network Planning

1. /SAPAPO/MC90 - Release Demand Planning to Supply Network Planning
In the above t.code i am not able to change the target planning area- it has greyed out
2. I need thisto be changed becuase i have defined my own snp planning area.
any clues how to do this >
reg
dsk

hi dsk
Dont worry about the greyed out target planning area in the "release :extended" option. It is the default. In general if you release the forecast from a demand planning book , it means that you are releasing the foreacast values from the time series live cache to order live cache. That is the forecast value which was just a quantity value in the time series live cache will now be associated to a specific category.
Once you release the forecast from DP to SNP you should be able to see the forecast value in all the SNP planning books that have forecast key figure. The forecast is not released to a specific planning book, it is released to the order network and will be available to view in all SNP planning books. So just go ahead and execute MC90 . After that you can make sure if the values are reflecting in SNP by going to /n/sapapo/rrp3 and checking the material . You should be able to see values under cateogry "FC Req". After this you can try loading the material in planning book and u must be able to view the results.
Thanks
Saradha

Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help the client in Data Mapping activity.

Hello All,
Is there any Data Mapping document Between S&OP ( model that uses supply planning operator ) and SAP ECC that I will help in Data Mapping activity.
Thanks,
Mownesh

There are standard templates in HCI data sources.
e.g. 1) Customer Master data template is SOP_MD_CustomerMaster for extracting master data from SAP ECC and load it to S&OP
KNVP is the table for customer in ECC from that you can select the fields as required
KUNNR for customer Number
ADRNR for Address
List of a few commonly used table names of ECC:
Product Related:
MARA – Material Master (MATNR)
MARC – Material Master with Plant Data (MATNR, WERKS)
MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)
MAKT – Material Master Material Descriptions (MATNR, MATKL)
MBEW – Material Valuation Data (MATNR, BWTAR)
MVKE – Material Master : Sales related Data
MDKP, MDTB – MRP related Data( Header, Item)
MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)
Vendor/Supplier related:
LFA1 – vendor data (LIFNR)
LFB1 -- Company Code Segment : Vendor Data(LIFNR, BUKRS)
LFC1 -- FI Related Vendor Data (LIFNR, BELNR)
LFM1 – Pur. Orgn. Related Vendor Data (LIFNR, EKORG)
PReq/PO, BOM Related:
EBAN – Pur. Req. Data( BANFN, BNFPO, BADAT, MATNR)
EINA – Purchase Info. Record(General Data)(INFNR, MATNR, LIFNR)
EINE – Purchase Info. Record (pur. Orgn. Data) (INFNR, EKORG)
ELBK, ELBN, ELBP – Vendor Evaluation Related Data
EKKO – PO Data (Header) (EBELN, BSTYP, BSART)
EKPO – PO Data (Item) (EBELN, EBELP, MATNR)
Pur. Req., RFQ and PO are differentiated by Doc Type (BSTYP) in EKKO table.
For RFQ it is ‘A’ and for PO it is ‘F’
MKPF – GRN Data (Header) (EBELN, BLDAT, BUDAT, XBLNR, BKTXT)
MSEG – GRN Data(Item) MBLNR, BWART, LIFNR, MATNR, EBELN)
Apart from this there are lot of tables which begin with ‘M’ & ‘E’, but we
use the following very often.
EQUK – Quota (Header)(QUNUM, MATNR)
EQUP – Quota (Item) (QUNUM, QUPOS, LIFNR)
EKBE – PO History Data (EBELN, EBELP, BELNR, BLDAT, MATNR, VGABE)
EKBZ – PO History with Delivery Costs(EBELN, BELNR, LIFNR, XBLNR)
EKET – Schedule lines data of a PO(EBELN, EINDT, SLFDT)
EKES – Vendor Confirmations Data (EBELN, EBTYP, EINDT, XBLNR)
T163F – Confirmation Texts (EBTYP, EBTXT)
T156 – Movement Types (BWARE)
T024 – Purchasing Groups
T024E – Purchase Organizations
T163 – Item Category’s in Purchasing Documents(PSTYP)
T149D – Valuation Types
T134 – Material Types
FVLK – Delivery Types
STKO, STPO – BOM(Bill Of Material) related Data (Header & Item)
STPU, STPN, STST, STZU – BOM Related Tables
RKPF, RBKP, RSEG (Header & Item) – MM – FI Related Data
KONO, KONH – Pricing data
T006 – Basic Unit Of Measurements
Customer/Sales Order Related:
VBAK : Sales Document(Header Data) (VBELN)
VBAP : Sales Document(Item Data) (VBELN, POSNR, MATNR, ARKTX, CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP Field) in VBAK, VBAP Tables for Enquiry VBTYP = A, for Quotation ‘B’ & for Order it is ‘C’.)
LIKP : Delivery Table(Header Data) (VBELN, LFART, KUNNR, WADAT, INCOL)
LIPS : Delivery Table(Item Data)(VBELN, POSNR, WERKS, LGORT, MATNR, VGBEL)
(LIPS – VBGELN = VBAK- VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK : Shipment Table(Header Data) (TKNUM)
VTTP : Shipment Table (Item Data)(TKNUM, TPNUM, VBELN)
(VTTP – VBELN = LIKP – VBELN)
VBRK : Billing Table(Header Data) (VBELN, FKART, BELNF)
VBRP : Billing Table(Item Data) (VBELN, POSNR, FKIMG, NEWR, VGBEL, VGPOS)
(VERP – AUBEL = VBAK- VBELN, VBRP – VBEL = LIKP – VBELN)
Apart from these tables there are lot of other tables which starts with ‘V’, but we use the
following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header) (VBELN, VBTYP)
VBTYP = ‘C’ (Sales Order) VBTYP = ‘L’(Delivery) VBTYP = ‘M’(Invoice)
VBUP: Sales Documents status & Admin. Data(Item) (VBELN, POSNR)
VBEP : Sales Document Schedule Lines Data (VBELN, POSNR, EDATU, WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN, ZTERM)
VBFA: Sales Document flow data(VBELV, VBELN, POSNV, VBTYP)
VBPA: Partner functions Data(VBELN, PARVW, KUNNR, LIFNR)
TVLKT: Delivery Type: Texts(LFART, VTEXT)
KNA1, KNB1, KNC1 : Customer Master Data and Other Partner’s Data(KUNNR,
NAME1,LAND1)
KNVK: Customer Master Contact Person(PARNR, KUNNR)
KNVV: Customer Master Sales Data.
LFA1, LFB1, LFC1: Vendor Master Data(To get Transporter data)(LIFNR, NAME1, ORT01)
MARA, MARC, MARD : Material Master Data(Basic, Plant, St. Location Views)
TVKO: Sales Organizations(VKORG)
TVKOV: Distribution Channels(VTWEG)
TVTA: Divisions(SPART)
TVKBZ: Sales Office(VKBUR)
TVBVK: Sales Group(VKGRP)
T077D: Customer Account Group(KTOKD)
T001W: Plants(WERKS)
T001L: Storage Locations(LGORT)
TWLAD: To get address of Storage Location and Plant(LGORT, ADRNR)
TVAU: Sales Document (Order) Types
KONV: Condition Types (pricing) (KNUMV, KSCHL, KWETR)
T685T: Condition Types Texts.
ADRC: To get Addresses of Partners
VBBE, VBBS: Sales Requirements Data
VBKA: Sales Activities Data
VBPV: Sales Document Product Proposal
Based on the functionality you can search ECC table names and fields
Hope this information is helpful for you.
Thanks and Regards,
Anjali

RE: Using interfaces to alleviate supplier plan visibilityproblems

Martin,
I presented a similar topic at Forum98, and this year I will be expanding on
the concept to talk about interchangeability of components. Breaking
supplier plan dependencies is only one of the reasons to implement a similar
strategy.
The short answer to your question is that you define the method signatures
and virtual attributes in the interface, which serves as a supplier to your
project and to the implementation. Then at run-time, you dynamically load
the library containing the appropriate implementation. The only supplier
dependencies are the actual interface definitions, which carry no baggage
with them.
This solution works for most situations, but there are a couple of instances
where it gets a little more complicated. Most notably, Forte does not allow
dynamic loading of a library that uses a Service object. For that, you must
use the Forte name service and bind to a proxy class at run-time. The proxy
class can be pretty much a do-nothing class, since it will be replaced at
run-time, but Forte will not bind to the interface itself.
I hope this helps - If you have any other questions, let me know.
Jeanne
-----Original Message-----
From: [email protected]
[<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Martin G Nystrom
Sent: Thursday, April 15, 1999 4:13 PM
To: [email protected]
Subject: Using interfaces to alleviate supplier plan visibility problems
At FORUM97, someone from Born presented a paper on how to use interfaces to
get around problems with supplier plan setups that restrict visibility.
Does
anyone have this presentation or can offer any pointers?
-martin
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

Jeanne Hesler wrote:
>
The work-around was to include the c library as a supplier to the
project that will be using it. It's a little ugly, but it works. In
your case, you would need to include both libraries. It should not
cause platform problems, because even though it is a supplier, it will
not actually get loaded until you ask for it, and you will only ask for
the right one for the platform you are on. Just be sure that what you
include as a supplier is a library, and not a source project.Thank you so much! I tried this out last night and it works great! The
only downside is that at deployment time, Forte will require the C
library to be installed even on the platforms that don't support it, but
that's a small price to pay for the benefits we're getting. And maybe
someday Forte will fix the bug. :) Again, thanks for your help.
You should be able to use FindLibrary to load a dll, because that's what
you would be doing if you were using compiled libraries.I don't actually need to do this now, but I did figure out what I was
doing wrong when I tried this yesterday. Our DLL name was slightly
different from the name of the project directory, but I had it coded as
if it were the same. So of course Forte couldn't find the library to
load. Also, Forte apparently looks first for the compiled library and
then for the interpreted library, so when I was getting the error
message, the error message referred to the name of the interpreted
library and I assumed that's all it had looked for. Sure helps when you
spell things right!
Dale
=================================
Dale V. Georg
Senior Systems Analyst
Indus Consultancy Services
[email protected]
=================================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

IBP 4.0 FP1 Patch 2 - Need more info on new features in Supply Planning

Hi All,
I was reading the SAP help and some of the new features are not very clear to me, if you have clarity around it please read and help me to get more clarity.
As per SAP Help,The following features are now available in IBP for supply:
Separate lead time units of measure can be defined for use in multiple planning areas depending on different time granularities.
My Query - Where do we define it? I do not see any additional attribute in the MDT where lead time is present but don't see any attribute to define lead time units or any other different settings in the planning area so how can we define this?
Static periods of supply are taken into account as input for the inventory target, with projected periods of coverage provided as output.
My Query - What exactly has changed and which are the new key figures here to support this? I could not understand this from reading the above text.
Independent demand is taken into account as input at the product location, in addition to the distribution demand from other nodes and customer demand.
The optimizer algorithm supports the Non-Delivery Cost Rate key figure as input for the independent demand at the product location.
My Query - A new key figure "INDEPENDENTDEMAND" is available now @PERPRODLOC so first point is very clear but second point is very confusing to me as "Non delivery cost rate" is only defined @PERPRODCUST so how we will define the non delivery cost rate for independent demand which is at different planning level and if we are not able to define it how optimizer algorithm will support it? Ideally it needs to be at same level like consensus demand and Non delivery cost rate both @PERPRODCUST Level.
Thanks
Girish

Hi Mark,
While I'm not in your list of people to respond I figure I give it a go anyways :-)
The list of features you mentioned is a nice summary. One of the main release themes is data quality as you noticed. Apart from changes to the name&address functionality we also added the advanced matching and merging into this release. So you can use custom rules to match and merge data. This also allows you to do things like householding for customer data records. In essence we have now completed the integration of Pure*Integrate into Warehouse Builder.
The mapping debugger is another big thing. This allow you to walk through your mappings and see in detail what happes to the data.
The metadata change management is now in the UI. THis means there is now object level version management in Warehouse Builder via the UI. You can also compare versions and get a difference report.
As you mentioned there are a number of smaller and bigger features next to this. The idea for this release is to make OWB a top Data Quality product and allow you to do your ETL and DQ in one tool. Apart from that we have added usability features (debugger, N&A wizard) and we have added some features to solve specific problems.
Especially the corelated commit is interesting in that respect. You can now, in a map with multiple targets control the commit, and choose to either commit all targets or none, or commit them individually (current behavior).
As usual there is a lot more, as this is indeed a major release. Keep an eye on OTN for more collateral regarding the new features. We are currently updating the site to reflect the new stuff.
On the OLAP patch, both 9.0.4 and 9.2 will work equally well with the OLAP patch (when it is available). In 9.2 we added some small thing around composites. More about that when there is an OLAP patch to test this one on in a customer site.
I hope this answered the question, if not let me know.
Jean-Pierre

Releasing demand plan from DP into custom categories in SNP.

Hi Gurus,
I need to release the demand plan from DP into SNP custom categories Z1 thru Z4. The key figures that I mapped to these custom categories are created in a non-standard planning area (copied from 9ASNP02).
I am able to release the demand plan using category FA only. Can anyone help me in releasing demand plan into these custom categories in SNP.
Thanks,
Shiv.

Shiv
I did a F1 help on target category field in tcode /n/sapapo/mc90 and this is what i found
For the release of the demand plan to Supply Network Planning, you can specify a category that tells the system which category of orders to release to. An entry in this field is optional, but if you do enter a category it must be a category that represents sales orders or forecasts, such as FA or FB.
You can also release to categories you have created yourself. This allows you to distinguish, for example, between different forecast priorities.
The system proceeds as follows:
1. Has a category been entered in the release profile? If yes, this category is used.
2. If no, has a category been set in the definition of the requirements strategy in Customizing? (You define the product's strategy in the Proposed strategy field on the Demand tab of the product master record.) If yes, this category is used.
3. If no, category FA (forecasts) is used.
So as the F1 help says in the release transaction /n/sapapo/mc90 did you try giving the custom categories ? Also i have one more idea - after the forecast gets released to category FA , copy it to a key figure that is assigned custom cateogries Z1 to Z4.
But just want to understand something . Why do you want to release it to a custom cateory instead of FA ? How are you going to handle the consumption of forecasts by sales orders if you release it to custom category. I think releasing it to a custom category will make your process more complicated since you are altering the standard SAP functionality.
Thanks
Aparna

Supplier plans - revisited

Hi People,
Some time ago, a forte developer (Kevin Klein) submitted a pex file to the User Group that would graphically display the suppler plan relationships between projects of a workspace.
When I applied this to our application, we got ... a mess (we have over 60 projects in our application.) I started messing around with the code and ended with a modified application, which is attached as a .pex file.
A list of additional functions is as follows:
Move any project node (for better visibility).
Redraw project lines based on project node selected.
Color-coded "supplied by" and "supplier to" relationship lines.
List supplied by and supplier to projects.
View Service Objects.
Clear all Non-connected nodes (for print clarity).
Print:
Reduce 'map' to print on a single page.
Add title to output.
Change dimensions.
Save a Project 'Map'.
Open a previously saved 'map'.
Modify settings through a preference window.
Etc.. etc..
O.K. so I went a little overboard, you gotta have something to do between compiles. :^)
To load the tool into your repository, run the following FSCRIPT commands:
Setworkspace (whatevernameyouwantthispexin)
Open
modlogger +(cfg:c4:2)
includepublicproj configuration
importplan SupplyGraph.pex
commit
quit
When you run the tool, (you may run it from running man) a warning window displays, indicating to use at your own risk. (You can suppress this annoying little window in the preferences.) After clicking on O.K., a small window will pop up, select 'create' under the 'file menu. Another window will display prompting you to select a workspace contained in the repository.
After you click "OK", it will crunch for a while and then display the project graph. The relationship lines will be suppressed for clarity.
To see the supplier relationships for any given plan, simply click on it once with the mouse.
You can right click any node and select any of the options. You can print the graph and do other things from the menu.
As Kevin did, I am hereby releasing this tool, without any warranty or support, into the public domain. Use it at your own risk! This applications makes use of unsupported methods. It may not work with future version of the 4GL.
If you find any serious bugs, wish to suggest some enhancements, or you're having problems running it, please feel free to contact me, with the caveat: this is an unsupported tool.
-later
-labeaux
Labeaux Schiek
DHS
Springfield, Ill, USA

check out Forte tech note 10448, order for importing projects.
There are a couple of postings for developer's apps as well in the archive.
-----Original Message-----
From: Kevin Klein [SMTP:[email protected]]
Sent: Wednesday, January 27, 1999 10:24 AM
To: Forte Users
Subject: Supplier plans
Does any one know of a Forte or 3rd party utility to print out the
supplier plan graph for an application? We are in the process of
modularizing our application using libraries and would find this
information very useful. I already know how to use FSCRIPT to show the
suppliers for an individual plan, but I'm interested in seeing the
supplier relationships for an entire application. Ideas, anyone?
Kevin Klein
Sycamore Group, LLC
Milwaukee, Wisconsin, USA
Mankind, when left to themselves, are unfit for their own government.
-- George Washington << File: Kevin Klein.vcf >> -
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Restrict release of planned orders

Hi,
I am working in ASCP - and my user would like the ability to restrict the release of planned orders by either planner code or user ID. Is there a way I can do this via profile option, or form personalization, or anything else?
Please provide insight on other ways to achieve this!
Thanks
Valeria

Hi,
Yes but in that case the responsibility being used to release the planned orders should not have access on any OU.
Below is the other thread where i gave the solution for requisitions.
Release from Planner's workbench auto-triggers WIP Mass Load, how do we restrict
Please let me know if you are interested and we can do it at user levels also if can't implemented at resp level..
Thanks,
Abhishek Sharma
Please mark the post correct or helpful, if answered

Release of Planned Orders from ASCP to Internal requisition

Hi All,
Is there a way to stop creation of ISO from IR which is released from ASCP Workbench?
As per my knowledge, when we release a Planned Order, it will create an IR and ISO automatically. There is no such functionality like in Purchasing side where we can use ASL to restrict the PO creation process.
Thanks for your pointers.
Regards,
N

Hi,
Yes but in that case the responsibility being used to release the planned orders should not have access on any OU.
Below is the other thread where i gave the solution for requisitions.
Release from Planner's workbench auto-triggers WIP Mass Load, how do we restrict
Please let me know if you are interested and we can do it at user levels also if can't implemented at resp level..
Thanks,
Abhishek Sharma
Please mark the post correct or helpful, if answered

Releasing Supply Plans to DP using RTSCOPY

Similar Messages

Maybe you are looking for