[Axapta-Knowledge-Village] Records in Report

[Rajkumar]

Dear All,

I just want to know that if there are 'n' lines in report for a 
particular query,then I have to display the first record with all 
the fields displayed,then the other lines for the same query should 
not display few fields.

I cant use the controlname.visible for the same.Is there anyother 
ways that i can do this using some query or select conditions. If so 
please let me know where to write, whther in fetch or send or 
executesection of that body.

If I use Programmablesection for that values alone, How can i stop 
the records for the query, as the same records are printed again 
with all the values displayed.

Seeking for help how to proceed.

Regards,
Raj

RE: [Axapta-Knowledge-Village] Changning the dimension group of items

[Anand Rathi]

Hi Madhu,
   
  You can change the dimension group but it may be a dirty method and i am not 
completely aware of the reurcussion of the same:
   
  Approach can be 
   
  1. Create a Dimension Group you wish to under the Inventory Dimension Group 
Set up.
  2. Use excel template and fill the Item and the changed dimension group as 
the dimension group for the respectiveitem. Keep other info for the item as 
same.
  3. Upload the Item Master and select the option which is used for update.
  4. Go to Item Master and you will find that the Dimension Group has been 
changed for the Item as per excel.
  5. The transactions henceforth made will consider the Dimension Group as 
attached above,
   
  
James Flavell <[EMAIL PROTECTED]> wrote:
  You can change as along as all inventtrans are closed. We have done 
this by
writing off all the stock balance, change dimension then bring back in stock

-Original Message-
From: Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Akshay
Sent: 27 September 2007 15:33
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: Re: [Axapta-Knowledge-Village] Changning the dimension group of
items

Sorry, as a standard fit, once transactions are passed, you cannot change
the dimensions. Every Inventory transactions points to a certain dimnesion
combination (inventDimId). An item having transactions with one dimension
grp cannot suddenly change the dimension grp and hence the inventory
dimension combinations. Your workaround is to create a new item and
discontinue usage of the older.

On 9/27/07, madhubabu_r <[EMAIL PROTECTED]> wrote:
>
> I am getting this warning message when I am changing the Dimension
> Group of an Item in the Item Master. I had done some transactions on
> this item.
>
> Message (12:40:11)
> The new dimension group cannot be assigned. Other financial dimensions
> apply and physical inventory transactions might exist and/or financial
> inventory transactions are not fully settled.
>
> Is there any way out to change the dimension group of this item???
>
> Thanks and best regards,
>
> Madhu
>
> 
>

[Non-text portions of this message have been removed]

Sharing the knowledge on Axapta.
Visit www.frappr.com/axapta for axapta friends.

Come and choose your preferred name for Microsoft Dynamics AX on the Axapta
Knowledge Village, Visit www.axapta-knowledge-village.tk

Yahoo! Groups Links



 

   
-
Yahoo! oneSearch: Finally,  mobile search that gives answers, not web links. 

[Non-text portions of this message have been removed]

[Axapta-Knowledge-Village] BOM Explosion at PO Lines

[Anand Rathi]

HI All,
   
  Is there any option in Ax, through which BOM explosion in PO Lines will 
account for both Main Item and the components of BOM of such Main Items.
   
  The scenario is to when Packing Slip is posted, client need to account for 
both the Main Item ordered for and also the BOM components available for such 
Item. Any input will be appreciated..
   
   
  thanks
   

   
-
Shape Yahoo! in your own image.  Join our Network Research Panel today!

[Non-text portions of this message have been removed]

RE: [Axapta-Knowledge-Village] Confirm deletion message

[prasad pendyala]

Hi
  if you want to change the Description of the message.Go for Label Editor 
  and add  your messgae in the Find Textbox to search the message 
   
  Ax Searches the message and gives a list of messages .
   
  select the one which is your intended message 
  and change the Description.
   
  It Changes.

Faiqa <[EMAIL PROTECTED]> wrote:
  

Tools>>Options>>Confirmation tab

Regards,

Faiqa

From: Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of bryanevil
Sent: Thursday, September 27, 2007 7:09 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Confirm deletion message

Hi all,

How can I change the Confirm deletion message for my custom form?
For Example, when you try to delete an Sales Order, it pop out a
Confirm deletion box said "You are about to delete a record in Sales
orders. Delete record?", how can I change it? Thank you. 

Regards,
Bryan

[Non-text portions of this message have been removed]



 



  Prasad.Pendyala


   
-
 Explore your hobbies and interests. Click here to begin.

[Non-text portions of this message have been removed]

Re: [Axapta-Knowledge-Village] Re: Excel templates for Uploading opening Stock

[Srivastava Ashish]

I have written a job that will help to create movement journal and post it.
Try this job

static void MovementJournalImportExcel(Args _args)
{
 InventJournalTrans inventJournalTrans;
 InventDim  inventDim;
 InventJournalTable inventJournalTable;
 InventJournalCheckPost journalCheckPost;
 InventJournalIdjournalId;
 journalTableData   journalTabledata;
 InventBatchinventBatch;
 InventBatchlocalInventBatch;
 NumberSeq  numberSeq;
 NumberSequenceReferencenumberSequenceReference;
 InventSerial   inventSerial;
 InventSerial   localinventSerial;
 int j,countno=0,i,k;
 real Scarp;
 FilenameOpenfilename;

 Sysexcelapplication excelapp=sysexcelapplication::construct();
 sysexcelworksheet excelworksheet;
 sysexcelrange excelrange;
 sysexcelcells excelcells;
// comvariant cellvalue=new comvariant();
;

// Creating Journal Header
inventJournaltable.initValue();
inventJournalTable.JournalNameId = 'ERecover';
numberSeq = new NumberSeq();
numberSequenceReference = InventParameters::numRefInventJournalId();
numberseq = NumberSeq::newGetNum(numberSequenceReference);

inventJournalTable.JournalId = numberseq.num();
inventJournalTable.Description = InventJournalName::find(
inventJournalTable.JournalNameId).Description;
inventJournalTable.insert();


excelapp.workbooks().open('C:\\Documents and
Settings\\asrivastava\\Desktop\\ElectronicData_OnlyWstatus_10032007.xls');
excelworksheet=excelapp.worksheets().itemFromNum(1);
excelcells=excelworksheet.cells();

// Creating Unit Numbers
 for(i=301;i<=5600;i++)
 {
inventBatch.clear();
inventBatch.initValue();
inventBatch.itemId = excelcells.item(i,11).value().bStr();
inventBatch.inventBatchId = excelcells.item(i,1).value().bStr();
localinventBatch = InventBatch::find(inventBatch.inventBatchId,
inventBatch.itemId);

if(!localinventBatch)
{
inventBatch.OakSerialUnit = excelcells.item(i,2).value().bStr();
inventBatch.insert();
}
 }

//Creating Appartment Numbers
 for(k=1;k<=648;k++)
 {
inventSerial.clear();
inventSerial.initValue();
inventSerial.InventSerialId = excelcells.item(k,8).value().bStr();
inventSerial.ItemId = excelcells.item(k,11).value().bStr();
localinventSerial = InventSerial::find(inventSerial.InventSerialId,
inventSerial.ItemId);

if(!localInventSerial)
{
inventSerial.ProdDate = systemDateGet();
inventSerial.insert();
}
 }

 // Creating Journal Lines
 for(j=301;j<=5600;j++)
 {
inventJournalTrans.clear();
inventJournalTrans.initValue();
inventJournalTrans.TransDate = systemDateGet();
inventJournalTrans.LedgerAccountIdOffset = "9";
inventJournalTrans.JournalType = InventJournalType::Movement;
inventJournalTrans.JournalId = inventJournalTable.JournalId;
numberSeq = new NumberSeq();
numberSequenceReference =
InventParameters::numRefInventJournalVoucherId();
numberseq = NumberSeq::newGetNum(numberSequenceReference);

inventJournalTrans.Voucher = numberseq.num();
inventJournalTrans.ItemId  = excelcells.item
(j,11).value().bStr();
// defaulting branch and item name
inventJournalTrans.CostAmount  = InventTable::find(
inventJournalTrans.ItemId).inventTableModuleInvent().Price;
inventJournalTable = InventJournalTable::find(
inventJournalTrans.JournalId);
inventDim.InventLocationId =  excelcells.item
(j,10).value().bStr();
inventDim.inventBatchId= excelcells.item
(j,1).value().bStr();
inventDim.inventSerialId   = excelcells.item
(j,8).value().bStr();
inventJournalTrans.InventDimId =
inventDim::findOrCreate(inventDim).inventDimId;
inventJournalTrans.Qty = 1;
inventJournalTrans.AdjustmentNotes = "Initial Data Load";
inventJournalTrans.LineNum = j;


inventJournalTrans.insert();
 }


excelapp.workbooks().item(1).saved(true);
excelapp.workbooks().close();

// Posting Journal
journalTableData = JournalTableData::newTable(inventJournalTable);
journalTableData.updateBlock
(JournalBlockLevel::InUse,JournalBlockLevel::None);
if (!infolog.num(Exception::Error))
{
infolog.clear(0);
journalCheckPost =
InventjournalCheckPost::newJournalCheckPost(JournalCheckPostType::Post,InventJournalTable);
journalCheckPost.parmAutoBlock(true);
journalCheckPost.run();
}
 }



Regards

Ashish




On 10/7/07, madhubabu_r <[EMAIL PROTECTED]> wrote:
>
>   Hi Ashwani,
>
> Thanks for such a detailed information which would be useful to all
> our fello

RE: [Axapta-Knowledge-Village] Excel templates for Uploading opening Stock

[cfidler]

Agree Jens it is the simplist and the easist way of doing it.




> Hello there,
>
> There is another "trick" that you could use ... :-)
>
> Do not load records directly into InventTrans, since this table is one of
> the key tables in Ax. Instead, during quite a lot of implementations, I
> simply load data into InventJournalTable and InventJournalTrans.
>
> Once the data is in the journal, you simply use the built-in function to
> copy a journal. Once the journal is copied, the corresponding journal
> lines
> are now updated in such a way that you will be able to book the journal
> without problems.
>
> I use the same approach when importing sales orders/lines and purchase
> orders/lines. I simply import them as journals, after which I let Ax
> handle
> the rest when changing order type from Journal to Sales Order / Purchase
> Order.
>
> Hope this helps.
>
> /Jens
>
>   _
>
> From: Axapta-Knowledge-Village@yahoogroups.com
> [mailto:[EMAIL PROTECTED] On Behalf Of madhubabu_r
> Sent: Sunday, October 07, 2007 2:26 PM
> To: Axapta-Knowledge-Village@yahoogroups.com
> Subject: [Axapta-Knowledge-Village] Re: Excel templates for Uploading
> opening Stock
>
>
>
> Hi Ashwani,
>
> Thanks for such a detailed information which would be useful to all
> our fellow implementors.
>
> I could successfully upload the opening stock using
> InventJournalTable, InventJournalTrans and InventTrans. I have not
> included InventDim as the DimGroupIds of all the items already exists
> in InventDim table.
>
> I have to include InventTrans as I was getting an error that there
> should be transaction with status "Ordered". I have included
> InventTrans table with status Ordered of all the items.
>
> I have uploaded and then posted the Movement Journal. Now when you see
> the on-hand inventory you will see the items in Ordered as negative
> witht he quantity uploaded. Then I went to InventSum table and changed
> all those negative entries to "0".
>
> I have tested master scheduling and other functionalities. Its working
> fine.
>
> Please reply whether this is ok. As you have used a word
> "malfunctioing" I am worried.
>
> Awaiting your reply.
>
> Thanks and best regards,
>
> Madhu Babu Rapolu
>
> --- In Axapta-Knowledge-
> 
> [EMAIL PROTECTED], ASHWANI JAIN
> <[EMAIL PROTECTED]> wrote:
>>
>> Hi Madhu,
>>
>> Uploading the opening stock using manual activity is really a
> tedious job, but yes we can do a partial time saving for the creation
> of journal (Invent journal) and journal lines (Invent journal trans).
>>
>> At the time of creation of record in journal lines (Inventory
> journal Trans), system automatically search for inventdim and if not
> found, then create a new record in InventDim, else allocate the
> available one on the InventJournalTrans. After the creation of new
> record in InventDim, same numbr is allcoated to respective transaction
> based on Dimension combination.
>>
>> Different inventJournalTrans lines can have same inventDim id.
>>
>> So in addition to above two tables, you have to import another third
> table "InventDim".
>>
>> Now the question arises, how to pick / define the correct InventDim
> in the import file in Table InventJournalTrans, as this table does not
> have Dimensions (config, color, size, warehouse, location etc...)
>>
>> Because system allocates, this on the basis of unique combination of
> dimension, so in excel using concatenate formula, create a new column
> and put formula in that to get value. Now there must be unique values
> in this field (refer above bold sentence).
>>
>> Filter out the duplicates, and now you should have single record of
> each type.
>> Take the current data of InventDim table to Excel by copy paste. Do
> same concatenate column in this worksheet also in excel.
>>
>> now using the Vlookup formula of Excel, check in earlier inventdim,
> what is the inventdim of those records. you will find some records /
> rows in excel where you will not get any inventdim.
>>
>> Take those records in new worksheet for import in inventdim. When
> you import these records, system will create the inventdim id for
> those records. Put these new alocated number along with the previous
> that you find in the InventJournalTrans. Now you can import
> InventJournal and InventJournalTran Tables.
>>
>> After importing them, ensure that all lines will be having inventdim
> id and cross validate for the dimensions (config, color, size,
> warehouse, location etc...) in them for 5 - 10 records. If found
> satisfactory, then you just have to click the Post button.
>> System will post the same in inventTrans and inventsum, to update
> the inventory.
>>
>> We should not have to import the records in InventTrans / InventSum,
> because these tables are the heart of Dynamics Ax, which may later on
> result in malfunctioning of the system.
>>
>> This whole lenghty explaination appears to be difficult /
> complicated, but once you do it, you will find it