Layer Change Point - help?

I've read through numerous posts here about the same subject, but none answered my question.
I'm authoring a dual-layer project, total size is 8.4 GB. It consists of a feature, and the disc is literally packed with bonus extras (making of etc). I've tried making every chapter in the main feature the layer break, and even chapters in some of the extras, but when formatting itcontinually says that layer one's size has been exceeded. I 've also tried shifting the VTS files around, as suggested in the manual, but still no luck.
Can anybody help?

When your videots is loaded you will see a series of blue arrows next to all of the cells that you can use as layer breaks. Expand a VTS with a blue arrow, expand the PGC, expand the cell, until you see navpacks will blue arrows. Click on one of theses navpacks. in the info about this navpack you can see the total time elapsed from the nearest marker. You can also expand the preview window so that you can view exactly what part of the video this is.
Many thanks for your help. I have opened the video_ts file with DVDAfterEdit Demo. The blue arrow points to:
VTS4 (1 PGC) -> PGC 1 TT 4 (12 programs) ->PG 8 PTT 9 (1 cell) -> Cell 8 (1292 nav packs) -> and then V1C8 Nav Packs 594-857 are highligted with blue arrows.
How do I find what point this relates to in my DVD project? VTS 4 in my project is the main feature, although I'm unsure where this app is telling me the layer break should be. Does a layer break need to be a cpapter, or can I make the layer change any other way?
If you do not have any options you'll need to add markers to the project in Tracks where you think the LB can go. Uncheck the Type: Chapter option. This means it'll be a cell marker and will not impact the chapters in your project. Build again and open to see if the cells are available.
I have no options forthe layer change to occur on chapters. Where do I find Type: Chapter option? I don't see this anywhere.
G5, dual 2.7 Mac OS X (10.4.3)

Similar Messages

Layer Change Point question

In the disc information panel (DVDSP bottom right) the layer change point is set to a trailer on the disc. I'm unable to select the actual layer change point that the format -> disc/volume window brings up - is there a way around this?
The layer change (which I've also designated as chapter 31 of the main feature by checking the 'layer change' box) also appears to be different in each of the formatting/build options. I'm confused.
Message was edited by: Marc Morris

You can only have one break point. If you build first. Then bring up the Format Window you'll see the options you have not greyed out. If you add Markers (Cell/Chapter) to the project in hope of a better place for the break point you'll need to build again to see the options,
-Jake

Need help in Change pointer creation

Hi Guys ,
I have one issue ..Change pointer getting created for Vendor if i create it from the Custom Program But it has some problem while Using LSMW ..
I just want to Know whether is there any Config issue with LSMW,,
Please advice me how to slove this issue ..
Thanks in advance.
Prabhu.

hi
good
go through this link ,hope this ll help you to solve your problem
http://sap.niraj.tripod.com/id51.html
reward point if helpful.
thanks
mrutyun^

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

What is chang pointer

hi
what is change pointer
could u plz explain clearly

Hi,
Change pointers are the mechanism through which you can send data to another SAP system or external system if there is a change happening to specific fields of master data.
Change Pointer (Master Data Distribution)
Purpose
If you want to distribute master data changes with the SMD tool (Shared Master Data), changes to the master data objects are flagged for distribution by change pointers ( ® Master Data Distribution).
The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.
The master IDoc is then passed to the ALE layer, which sends it to all interested systems.
The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.
For more info
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
do the following steps for Change pointers ::
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
Regards,
Priyanka.

DVD Studio Pro Dual Layer Break Point Problem

I have a problem with a disc that I am burning. It is a dual layer (the break point is not set to seamless) with 1 movie that is about 3.6 GB and 1hr 23 min long, a 30 min slideshow, another 30 min extra and five other extras that total to about 20 min. I put the dual layer break point at the beginning of the slideshow, everything played fine on the computer, but on the Panasonic DVD player it just freezes at 35 seconds into the slideshow. Its never had a problem with DLs before. Itried the DVD on my softmodded Wii, on a program for it called WiiMC (it uses Mplayer) and everything played fine. I tried another burn where i set the break point to fifteen minutes before the end on the main 1:23 movie and on the DVD player it still froze at 35 seconds on the slideshow. Is there anything that you guys can suggest to help?

DVD+R or DVD-R?
http://documentation.apple.com/en/dvdstudiopro/usermanual/index.html#chapter=1%2 6section=9%26tasks=true
DVD+R Double-Layer
You can use DVD+R double-layer media, often referred to as DVD+R DL, for burning your dual-layer projects. With DVD+R double-layer media, DVD Studio Pro places the layer break point and sets the switch point to be nonseamless as specified in your project.
DVD+R double-layer discs require you to use the Opposite Track Path (OTP) direction setting when burning the disc. This means that the first layer must be larger than the second layer. See Setting the Dual-Layer Direction for more information.
While DVD+R double-layer discs allow you to burn your dual-layer projects, they tend to have more compatibility issues than the other types of DVD media.
DVD-R Dual-Layer
If your system contains a DVD drive that can write to the new DVD-R dual-layer media, you can burn your DVD project to it with DVD Studio Pro. However, there are several issues:
Because currently DVD Studio Pro has no way to identify DVD-R dual-layer media as having two layers, burning a dual-layer project to it results in the appearance of an alert message telling you that the DVD media may have insufficient room to hold the project. This message is based on the assumption that the disc is single layer. Both layers of the disc will be written to as needed, however, when you click Continue.
If you are burning a dual-layer project, the break point you set will not affect where the layer break actually occurs. Instead, the first layer is written to until filled, at which point the drive switches to writing to the second layer.
The switch between layers is a seamless layer change not supported by some DVD players, which may stop playing the disc when the switch point is reached.
Important: Do not use DVD-R dual-layer media unless these issues do not impact your project.

How to find - Customer Master IDoc was created Manually or by Change pointe

Hi all,
I have an IDoc(Customer master) number (which I have taken from the payload in SXMB_MONI). I would like to know whether this has been created by a user manually(BD14) or by a change pointer.
Please help.
Cheers
danus

Hi Vardharajan,
Yes I agree with you. What I mean by IDoc created by change pointer is - 'IDoc generated because a change(pointer) is tracked by the system', in other words, due to some change made to the data.
As you know, the other option of creating IDoc is by BDxx transaction. This option is usually used to push (unchanged) data.
So in essence, what I am interested to know is , has the IDoc been generated because someone made a change using say, VD02 / XD02 or pushed the data manually.
Please do ask, if anything is not clear.
cheers
danus

Activate change pointer for a new screen field in MM42/41

Hi,
I created a new screen field for Article master(MM41/42/43) under basic data. If there are changes made to this new field how will the system create a corresponding IDOC? does this have something to do with the change pointer thing?
Thanks,
Jeff

Hi Jeffrey,
first of all got transaction SALE :
ALE
-> Modeeling and Implementing
-> Master Data Distribution
-> Replication
-> Activate Change Pointer generally
Check if Changepointers are generally on.
Then goto BD50 and activate change pointers fpr message type.
Finally goto BD52 and check if your field is "watched".
After that you can generate idocs from BD21.
Hope it helps.

ALE/Change Pointer Configuration for ZSEGMENTS

Hello all,
I have been searching for a few days now trying to obtain my requirement with extending of an idoc. I am working with the following:
Message Type: HRMD_A
BASIC Type: HRMD_A06
Extension: ZHRMDA06
I extended the idoc because I wanted to include 2 extra infotypes which are not on that idoc. Infotypes 77 and 709.
Here is what I have completed so far.
WE30...Created ZSEGMENTS to include below.
WE31...Extended the HRMD_A idoc to include the ZSEGMENTS defined below.
WE82...Updated the output types and assignments to idoc.
BD61...Activate Change Pointers
BD50...Activated change pointer for HRMD_A.
I change the address field in infotype 0006.
Run the BD21...idoc is generated with the changes to address, everything looks good.
Do the same thing for the ethnic origin on infotype 77, no idoc is generated.
I turned on logging onto table PA0077.
I am evaluating the change logs via SCU3, and I am seeing my changes on the field.
What I have tried...
I have tried creating a object in t-code SCDO (ZTEST)
I have associated ZTEST with table/field PA0077-RACKY.
Tried running BD21...No iDoc generated.
I have been researching for a few days and it feels that this should be able to be done through configuration and not custom coding. Am I wrong to think that?
Has anyone ever did anything like this before which they can point to documentation or even the appropriate search criteria on the SCN forums.
Thanks in advance for your help!
Jason

Hi Jason,
I believe you have to enter the fields that trigger the changing pointer in tcode BD52. In my case these are the fields for BOM:
Regards,
Custodio

What is change pointer in ALE ?

Dear Guru,
1. What is change pointer in ALE and how to configure it ?
The process of configure please guide me !
Tanks and Regards,
Subash.

Hi,
Change pointers are R/3 objects that mark changes to SAP master data. Change pointers are managed by mechanisms in a Shared Master Data (SMD) tool and are based on Change Document (CD) objects. CD objects record the changes occurring to master data at a field level. These changes are stored in tables CDHDR (header table) and CDPOS (detail table). ALE configuration provides a link between CD objects and change pointers. Internal mechanisms update tables BDCP and BDCPS, which host the change pointers. While CD objects are application-data-specific, the processing status of change pointers is message-type-specific. Also, the ALE change pointers are activated first at a general level and then at the message-type level.
ALE provides powerful capabilities to capture changes occurring to master data and to distribute them via the IDOC interface. This feature can be used to keep two or more systems synchronized with respect to master data.
Steps to configure change Pointers:
1.Activate the change pointers globally(BD61)
2.Activate the change pointers for individual message types(BD50)
3.Schedule the program RBDMIDOC to run periodically on the sending system.
To Delete Change pointers use transaction BD22 and the standard program is RBDCPCLR
Remember You can see a check box in Further characteristics tab of the data element ( se11>enter data element>Further characteristics tab) for change document.
This check box is to bo checked to trigger change pointers.
please check out the following link for more information it might help you
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
http://help.sap.com/saphelp_470/helpdata/en/dc/eb683c00e8a646e10000000a11402f/frameset.htm
Regards,
Satish

Problem to create change pointer for custom message type - Idoc creation

Hi,
We want to create IDOC and send it out when the data of "planning calendar" changes. So we are trying to generate change pointers whenever entries in Table T439I (Planniing calendar) data change.
We created a message type, activated change pointers generally and maintained change relevant fields for message type (not sure if this step is done correctly). But not getting any change pointer in table BDCP2 when I create a new planning calendar in MD25.
Can anybody help / guide?

Thanks once again,
I had linked idoc type and message type in we82. Now after i activate the change pointers. I try to generate the IDOC type using BD21. It gives me the error message :<b> "Message type ZP2PPROJ_MSG cannot be sent with change pointers"</b>
whereas in my segments i am using all the master data only (i.e. PRPS, PROJ,PRHI). Please throw some light on this.
Also please clarify, do i need to make an entry of this custome message type in the partner profile ?
Rgds
kewal.

Change pointer for Sales Order

Hi,
Using change pointers I want to create an IDOC when ever a specific field in the sales order line item is changed. I have activated the change pointer for message type ORDRSP. Also maintained the following entries in BD52
VERKBELEG(Object) VBAP(Table) ABGRU(field).
After this when I change this field at the sales order line item, it inserts entries into change pointer table.
But my problem is creating IDOC's from those change pointer entries. I am not sure which function module (MASTERIDOC_CREATE_XXXXX) works for this.
Anyhelp on this highly appreciated.
Thanks
Ram

Hi Ram,
I don't think so you can use change pointer for sales order changes. Usually, it is done through transaction code<b> NACE</b> - configuring condition for output type.
You can setup requeirement in procedure control to trigger IDoc ORDRSP for any changes in item level.
Hope this will help you and give an idea.
Regards,
Ferry Lianto

What is the use of change pointer technique in IDOC

hi
could anybody suggest me
what is the use of change pointer technique and how to use it
thank you
kalyan.

Change pointers are used for changes to the master data objects are flagged for distribution by SMD Tool.i.e.shared Master Data.
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61
The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.
The master IDoc is then passed to the ALE layer, which sends it to all interested systems.
The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.
You can increase the rate of processing by using the Analyze Change Pointer and Reorganize Change Pointer functions.

Change Pointer RBDMIDOC in SRM Replication

Hi Experts ,
We have ECC 6.04 with SRM7.0. We replicated HR Org Structure from ECC to SRM.
Out of 10000 Employee , only 2000 Employee will sue SRM, So I wish to replicate only 1500 Employee as initial upload from ECC by eopy paste from EXCEL in PFAL selection screen. That is okay.
For changes & Delta , I will schedule Chnage Pointer RBDMIDOC in SRM.
1) My doubt is exatly what this Change Pointer will replicate to SRM (with matching to Filter setting ).... out of below ?
1. Changes to already replicated Employees in SRM
2. New created Employees after initial replication
3. Remainning Employees in initial replication as well ( i.e. 13000 )?
Is all these 3 cases will replicate to SRM ?
2) In case of change of one field value, will system send only that Value in IDoC or all the date of Employee again ?
Please suggest
Thanks
NAP

Hello sranjna ,
These are the steps for change pointer :
1. BD61 :Activate change pointer generally .
2. BD50 :Activate change pointer for message type.
3. BD21 :Create IDOC type from change pointers.
4.Save the content : create a variant .
5.For automatically process:go to SM36 :Create a job with the program "RBDMIDOC " and the variant you created.
Also see the link if you want :
[http://help.sap.com/saphelp_nw04/helpdata/EN/12/83e03c19758e71e10000000a114084/frameset.htm]
Good Luck,
Boaz

How to manually create layer breaking point for DVD9

Hello, I was wondering if someone could please tell me how I would go about to manually set the layer break point for a DVD9 project that I burned onto 2 DLT tapes. The total size of the DVD is 6.3GB.
I had used the "automatic" setting for burning the DLTs and sent them to a replicator. They came back saying that the layer 0 tape did not allow enough headroom for their Ripguard protection.
I've always used the automatic setting and this is the first time I am asked to manually set it. SO now I need to figure out how I can put a certain amount of data on one DLT tape and the rest on the other DLT.
I am a beginner at this so any help would be greatly appreciated.
Thank you!

Hi Eric,
Unfortunately the information you have regarding RipGuard and the ability to copy RipGuard protected discs is a little outdated.
Can RipGuard be broken? Yes, anything can be broken into, including the DoD Website by 14 yr old chinese students... but that doesn't mean there isn't value in protecting the DVD.
Also, RipGuard is regularly updated, just like Antivirus software, so while older versions of RipGuard can be broken more easily, the latest versions of RipGuard are significantly more difficult to circumvent by existing software.
But again, the point isn't to create the unbreakable 'holy grail' DVD copy protection, but rather to protect something of value.
When you leave your house in the morning, do you close your front door and lock it? Of course you do, but why? So no one will break in. But do you think locking up your house is really going to stop someone from going around to the side of the house and busting out a window if they really want to get in? Of course it wont. If someone wants to break into your house, they will find a way.
Same thing with DVDs. You lock your house because it provides a method of protection, a barrier to make it more difficult and to keep honest people honest. That's what RipGuard, or any copy protection software does.
So the question isn't why would you protect your DVD, but rather why wouldn't you? In most cases if you prevent just a few illegal copies of your DVD from being ripped, it has already more than paid for itself.

Layer Change Point - help?

Similar Messages

Maybe you are looking for